Re: ERwin character generation

actually, I've found most of the "interesting" DDL to be caused by the Physical Storage option on the Column dialog (not the Table dialog) during schema generation. (I'm using 3.5 here, I don't remember exactly where this was in 3.0, just that it was there). in this particular case, I bet that ERwin is putting the char(20) fields first because the database that you are generating to will put them first on disk since it can more accurately allocate space for columns whose width has been limited. turning off Column/Physical Storage should fix your problem...

• mark

In article <376EB231.934825FD_at_exesolutions.com>,   "Daniel A. Morgan" <dmorgan_at_exesolutions.com> wrote:
> Column order is unimportant. And ERwin has a history of writing
"interesting"
> SQL. If you are using version 3.5 see whether you are defining your
columns in
> the LOGICAL or the PHYSICAL window.
>
> It is always best with ERwin to have it create the SQL as a text file
and then
> proof-read and edit it.
>
> Daniel A. Morgan
>
> Jplahman wrote:
>
> > Hi:
> >
> > I'm new to ERwin, so please be patient.
> >
> > I've designed a table with the following columns:
> >
> > LimitCode: Char(20)
> > LimitType: Char
> > LimitName: Char(20)
> > HoldUse: Char
> > Aim: Float
> > MinTol: Float
> > MaxTol: Float
> >
> > LimitCode and LimitType form the primary key.
> >
> > When ERwin generates the table, the order of the table is:
LimitCode,
> > LimitName, LimitType, HoldUse, Aim, MinTol, MaxTol. Why does ERwin
do this?
> >
> > Thank you
> >
> > Jim
> > JPL
>
>

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't. Received on Mon Jun 21 1999 - 19:56:21 CDT