From: sera@... (Francis Hwang)
Date: 2004-04-24T04:09:08+09:00
Subject: Re: The quest for opensource database...

"Useko Netsumi" <usenets_remote_this@earthlink.net> wrote in message news:<c66462$8ber2$1@ID-205437.news.uni-berlin.de>...
> May be we can get away with the strored procedures. Why would one do
> manipulation of the data inside a database engine, right? The function of
> database is to store and retrieve information, that's it. Beyond that you
> really stretch it and this where scripting language such as Ruby comes in.
> 
> But for trigger, to write a commercial grade transaction processing
> application, you definitely need trigger. Trigger will aid
> programmers/designer to ensure certain consistency checking happen
> before/after certain opearation. How would you do that outside the database
> engine withouth kludging it?
> 

Well, you could write an object-relational mapping layer that executes
triggers in the code before hitting the database. Then you could write
a mock database underneath that which allows you to actually unit-test
your triggers without having to slowdown to hit a live database. I
did:

http://lafcadio.rubyforge.org/

This is newer stuff and no dobut a lot less robust than, say, the
stuff you get in Oracle. But I use this feature routinely in
production work, and I really really really like being able to unit
test my triggers.

Francis