Book a Demo

Author Topic: column data type bug  (Read 3511 times)

megoo80

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
column data type bug
« on: July 27, 2006, 06:15:12 am »
Hi all,

I have a problem with data modeling in enterprise achitect version 5.0 build 772 ......

i generate DDL script and for some tables it appear like that:

CREATE TABLE TblAgainst (
IntOrderDealer numeric DEFAULT  NOT NULL,IntOrderCode int DEFAULT  NOT NULL,
IntDealerType int DEFAULT  NOT NULL
)

and when i runned the script on sql server he output errors of "incorrect syntax near not"

when i returned back to the data model in enterprise architect and i tried to select the columns to see their type..... the columns appear with their dedicated types but when you click one of them to update the data type not appear on the combobox of data types and when i clicked the combobox to show the existed datatypes the combobox appears to be empty ???

Does anyone has a solution to these problems?

thx

thomaskilian

  • Guest
Re: column data type bug
« Reply #1 on: July 27, 2006, 10:53:08 am »
I had a similar problem connected with code transformed classes (still with Sparx AFAIK). To get the types you have to go through the properties and then click the Columns button. Now you can see the dropdown.
Edit: btw. Sparx, will this be fixed in 6.5?
« Last Edit: July 27, 2006, 10:54:21 am by thomaskilian »

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: column data type bug
« Reply #2 on: July 27, 2006, 03:06:22 pm »
If the combo box for column types is empty then the database is probably not set properly for that table.  To set it open the Table properties.

The database type should be set properly in a transform.  Types however can't be guaranteed to be correct because the macro for converting types doesn't know every situation.

megoo80

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: column data type bug
« Reply #3 on: July 30, 2006, 02:23:44 am »
thanks simon this solves the problem :)