On Jul 7, 2009, at 3:09 PM, Scott M. Neal wrote:


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?  :-))

I don't use Postgresql, but I believe that the prototype "id" is the one to use for PKs and FKs. I see that there only seems to be an external type of integer for Postgress and even a LongNumber prototype which has a java datatype of Long, is still an integer in Postgress. Are postgress integers really longs?

Dave


                        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 protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjects%40avendasora.com

This email sent to [email protected]








_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to