SCO 507 + MYSQL

[Fairlight]

Four score and seven years--eh, screw that!
At about Thu, Sep 29, 2005 at 05:46:55AM -0400,
Walter Vaughan blabbed on about:
> 5.* is going after MS-SQL/Oracle with stored events and triggers

Weren't they also implementing views in 5.x, or is that slated for 6.x now?

FWIW, I think stored procedures are a real mixed blessing.  On one hand,
you have resourse savings by keeping procedures at the server level and
eliminating needless communications and more attendant potential fault
points.  On the other hand, it spreads out your programming so that it's
not all in one cohesive flow from the client-side application.

Personally, I would prefer it to be all client-side.  Comms is pretty
inexpensive unless you need to transfer a LOT of data for an operation.
But then, you have a choice whether to use stored procedures or not.  I'd
likely choose "not" about 90%+ of the time.  It just seems so sloppy to
have half your logic in one place, half in another, if you don't need to.
They're really something I think should be a last resort for "expensive"
operations.

YMMV.

mark->
-- 
There is no "I" in TEAM.
This would be the primary reason I've chosen not to join one.