Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ERwin character generation

0 views
Skip to first unread message

Jplahman

unread,
Jun 21, 1999, 3:00:00 AM6/21/99
to
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


Daniel A. Morgan

unread,
Jun 21, 1999, 3:00:00 AM6/21/99
to
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

bra...@my-deja.com

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to
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...@exesolutions.com>,


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

Jonathan Gennick

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to
On 21 Jun 1999 21:00:34 GMT, jpla...@cs.comnospam
(Jplahman) wrote:

>When ERwin generates the table, the order of the table is: LimitCode,
>LimitName, LimitType, HoldUse, Aim, MinTol, MaxTol. Why does ERwin do this?

Erwin is probably using the order in which you added the
columns to the model. I'm not sure how to change that in
Erwin, but you could have Erwin output the creation SQL to a
script file, and edit the script to change the order. I
never let Erwin make changes directly anyway. Another
alternative is not to worry about it. In your case, using
CHAR fields, I don't think that the column order will
matter.

Jonathan

_____________________________________________________
jona...@gennick.com
http://gennick.com
Brighten the Corner Where You Are


Jplahman

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to
In article <7kmmvg$qil$1...@nnrp1.deja.com>, bra...@my-deja.com writes:

> turning off Column/Physical
>Storage should fix your problem..

Turning off Physical Order during the generation phase fixed the problem.

Thanks a bunch!

Jim
JPL


Jplahman

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to
In article <377c02af...@netnews.worldnet.att.net>, jona...@gennick.com
(Jonathan Gennick) writes:

> In your case, using
>CHAR fields, I don't think that the column order will
>matter.

I want to use MS Access to fill in the table, rather than writing SQL code. By
setting up a simple MS Access form in the order in which I expect simplifies
the initiation of the table.

Again, thanks for your help

Jim
JPL


0 new messages