Book a Demo

Author Topic: Import DB schema from ODBC - comments losing line breaks  (Read 4173 times)

CTucker

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Import DB schema from ODBC - comments losing line breaks
« on: January 31, 2020, 06:39:32 am »
Is there a way to import DB comments without the line breaks being lost? 
I've tried unchecking the option "Tools > Options > Source Code Engineering > Remove hard breaks from comments on import", but that did not work.
I'm using Sparx EA 12.1 and I'm importing from an Oracle 12c DB.



Modesto Vega

  • EA Practitioner
  • ***
  • Posts: 1183
  • Karma: +30/-8
    • View Profile
Re: Import DB schema from ODBC - comments losing line breaks
« Reply #1 on: January 31, 2020, 08:46:04 pm »
The line breaks may actually not be lost. It may very well be that Sparx cannot render them. Do you know if they are {CR}{LF} or just {CR} or {LR}. Cannot remember how Oracle does this?

CTucker

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Import DB schema from ODBC - comments losing line breaks
« Reply #2 on: February 03, 2020, 07:07:38 am »
If I look at the comments in database all original comments have {CR}{LF} for line breaks.  When I look at the notes in Sparx EA (imported from DB comments) all {CR}{LF} appear to have been replaced by a single {space} character.


qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: Import DB schema from ODBC - comments losing line breaks
« Reply #3 on: February 03, 2020, 11:49:19 am »
It's the way they render notes. It's Sparxian, so to say. You can paste any RTF into notes and it looks fine - until you reload. Complex formatings are gone and only that Sparx-subset is kept.

q.

CTucker

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Import DB schema from ODBC - comments losing line breaks
« Reply #4 on: February 04, 2020, 03:32:54 pm »
What is interesting, the popup that appears in the diagrams when you hover over a table, still has the {CR}{LF} but it is gone in the NOTES field in the property sheet.  So in the repository it must still have the  {CR}{LF} stored.  I'll wait to see what happens when I generate DDL for the model.