On Aug 15, 2008, at 12:16 PM, Ondřej Čada wrote:
Chuck,
On Aug 15, 2008, at 9:00 PM, Chuck Hill wrote:
It's probably easier to wrap the same idea inside some simple
direct SQL statements.
If you are willing to be DB specific, an After Insert trigger might
be the best way to handle this. Just make sure the order number
attribute is not used for locking.
Ha... this looks like I can save some fun\b\b\b time!
The server is FrontBase and the possibility the client would ever
switch is completely negligible (at least one advantage here ;))
Low-level SQL is not exactly my cup of tea (to be frank I haven't
even know what triggers are!). Am reading on them in the docs the
very now and it looks pretty promising.
Sometimes the app is not the right level for solving the problem. I
do try to avoid things like this, but sometimes they are the best
solution.
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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]
