Re: EOModeler SQL generation
Re: EOModeler SQL generation
- Subject: Re: EOModeler SQL generation
- From: Dave Elsner <email@hidden>
- Date: Fri, 5 May 2006 09:31:27 +1000
Thanks
I never knew EOSynchronizationFactory or WODBUpdate existed I will
have to look into both of these thanks again.
On 04/05/2006, at 9:14 PM, Pierre Frisch wrote:
Depending on how often you need to do this you can write a bit of
Java code to handle that. Create you own subclass of EOEntity that
do the correct sorting of attributes (you need to overwrite the
attributes() method) add to your model for each of the entity
concerned a key entityClass = yourEOEntityClassName. Then use
EOSynchronizationFactory to generate the SQL statements required.
Pierre
On 4-May-06, at 12:06 AM, Dave Elsner wrote:
Thanks Sacha and Art.
This is what I expected (i.e copy EOModelers SQL, paste it into a
text editor). I was just hoping there would be a nicer way incase
I need to do it multiple times.
The purpose of this "seriously silly requirement" is so that when
the DBAs use their GUIs or SQL*Plus etc, they don't have to scroll
horizontally to find that the PK is in the 22nd column of a 35
column table, so that the most important keys can be found
instantly which is fair enough. But this seems a pain when I have
been using OpenBase for so long and can simply click and drag
columns in the order I want.
- David
On 04/05/2006, at 4:13 PM, Sacha Michel Mallais wrote:
On May 3, 2006, at 9:25 PM, Dave Elsner wrote:
After speaking with our Oracle DBA they would like columns name
for each table to be created in order of their significants when
the create table statements are ran.
i.e The Primary Key(s) should be first, the candidate keys then
foreign keys, then every thing else.
However the default in EOModeler is to order them alphabetically
is there any way around this? So I can customize the order on a
per table basis ?
Yes, there is a way around this: get a new DBA. That is a
seriously silly requirement.
I would prefer not to write the SQL by hand.
If the insanity persists, hand-coding is probably your best bet.
EOModeler's output is rather limited anyway, so its nice to be
able to replicate all the tweaks that you may have to do in a
single file.
sacha
--
Sacha Michel Mallais Senior Developer / President
Global Village Consulting Inc. http://www.global-village.net/
PGP Key ID: 7D757B65 AIM: smallais
"Good people do not need laws to tell them to act responsibly,
while bad people will find a way around the laws." -- Plato
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@spearway.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden