Hi, Thanks for the hint about using Prototypes, it is really useful.
That brought to my mine a questing that is a little out of the topic.
If you have an attribute prototyped as currencyAmount the precision is
set to 38 and the scale to 4. The Data Type suggested is
java.math.BigDecimal.
How are you guys controlling that the BigDecimal in your java class
does not have a value whit a scale superior of 4 before saving the
editing context to avoid an exception?
We are currently solving this just rounding the value before saving,
or in the validation method to ensure the scale is not superior that
the value defined in modeler. But one of the great things of
prototyping is that if for some reason I want to change the scale to 5
instead 4, all the attribute definition's that are using that
prototype will be updated, what about the BigDecimal?
Maybe I am wrong on thinking that I should be sure that the scale of
my BigDecimal must be less than or equals to the scale defined in the
modeler to avoid exception on saving.
How do you guys handle this?
On Jul 7, 2009, at 2: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 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/miguel%40toracom.net
This email sent to [email protected]
_______________________________
Ing. Miguel Angel Torres Avila
Director General
Tel: +52 (33) 3367 1892
Cel: +52 (33) 3106 8758
E-mail: [email protected]
www.toracom.net
_______________________________________________
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]
