From: Damon T. <da...@ra...> - 2001-05-04 16:27:06
|
I haven't looked too closely at the code but here are my thoughts... a) letting the database manage business logic with triggers and constraints is a good thing for design and performance reasons b) unfortunately, most rdbms have proprietary formats for triggers so writing a trigger for Postgres would either eliminate other rdbms or necessitate different database code for different rdbms. Damon Quoting Benjamin Lee <ben...@co...>: > This is just a thought... > > I was going through the code, and I was wondering to myself whether it > would robustify matters any to move the 'update_balance' code into the > database layer with triggers and then have the 'chart' table updated > by the triggers. > > Using triggers would of course put MySQL in a bit of a muddle, but it > would simplify the business processes in the application layer. I was > almost confused reading the bits between old_this and new_this. ;-) > > I might stuff around with this trigger idea in the not too distant > future. > > Comments? > > P.S. Don't flame me about MySQL. I love MySQL; and in fact, I'm more > of a newcomer to PostgreSQL. I'm just poking around and the like. > > -- > B. http://makelinux.org/ "Always real." > http://realthought.net/ > > Damon Torgerson President, Ranksix Inc. da...@ra... 250.884.7171 |