Re: WOLips Entity Modeler SQL Generation and WO 5.4
Re: WOLips Entity Modeler SQL Generation and WO 5.4
- Subject: Re: WOLips Entity Modeler SQL Generation and WO 5.4
- From: Johann Werner <email@hidden>
- Date: Tue, 7 Jul 2009 21:42:01 +0200
Am 07.07.2009 um 21:09 schrieb Scott M. Neal:
On Jun 30, 2009, at 5:43 PM, David Avendasora wrote:
On Jun 30, 2009, at 8:29 PM, Scott M. Neal wrote:
Well, if you're looking for excuses to "upgrade" things, maybe
transition to using Prototypes. I'm sure the Postgress Prototypes
in Wonder's ERPrototypes will all have the proper External Types. :-)
Wow, thank you Dave, that DOES make things substantially easier
(and less prone to error--sure enough, had a missing external type in
one of the entities). All this modern fanciness, still getting used
to it...
Now my question is, for the Postgresql prototypes, which one
is recommended to use for primary keys? Googling reveals some people
using long (called longNumber in prototypes), which is what I
historically
used, while others are using varchar (but not consistent regarding
size:
10? 100? 10,000,000? :-))
Why don't you just choose the most obvious prototype: 'id'? Life can
be so easy ;-)
jw
Thank you,
Scott
Otherwise, you should be able to just select one entity at a time
and click the SQL button and see which one(s) generate the error. I
see pretty clear error messages with this, that say exactly what
external type is not recognized.
Dave
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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