• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WOLips Entity Modeler SQL Generation and WO 5.4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WOLips Entity Modeler SQL Generation and WO 5.4


  • Subject: Re: WOLips Entity Modeler SQL Generation and WO 5.4
  • From: David Avendasora <email@hidden>
  • Date: Tue, 7 Jul 2009 16:58:57 -0400


On Jul 7, 2009, at 4:53 PM, Kieran Kelleher wrote:

.... and if you want even more modern 'fanciness', you can turn on ERXModel as your eomodel class in Wonder, you can have custom prototypes of your own in other eomodel files and with the right naming convention (of the eomodel file) and using the same prototype attribute name, you "override" the built in prototypes with your own custom definitions..... useful for the BigDecimal scales etc. :-;

There he goes again winking with his chin. I believe he _is_ insane. :-P


See ERXModel api (or source) for more details.

Regards, Kieran

On Jul 7, 2009, at 3:42 PM, Johann Werner wrote:


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




_______________________________________________ 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

_______________________________________________ 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



_______________________________________________ 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
References: 
 >Re: WOLips Entity Modeler SQL Generation and WO 5.4 (From: "Scott M. Neal" <email@hidden>)
 >Re: WOLips Entity Modeler SQL Generation and WO 5.4 (From: Johann Werner <email@hidden>)
 >Re: WOLips Entity Modeler SQL Generation and WO 5.4 (From: Kieran Kelleher <email@hidden>)

  • Prev by Date: Re: WOLips Entity Modeler SQL Generation and WO 5.4
  • Next by Date: Re: WOLips Entity Modeler SQL Generation and WO 5.4
  • Previous by thread: Re: WOLips Entity Modeler SQL Generation and WO 5.4
  • Next by thread: Re: WOLips Entity Modeler SQL Generation and WO 5.4
  • Index(es):
    • Date
    • Thread