Re: How to handle trigger from database.
Re: How to handle trigger from database.
- Subject: Re: How to handle trigger from database.
- From: Christian Pekeler <email@hidden>
- Date: Mon, 20 Jun 2005 16:07:51 -0600
I have triggers on the database such that if a given row is updated,
the database will generate a notification to any client that is
looking at that row.
I prefer architectures where the database is the private store of one
application (or a set of related applications built using the same
technology - WO/EOF in our case). So if you need a different kind of
application to change data, let it go trough the application that own
the DB instead of giving it direct access to the DB.
Just recently I was involved in a project that heavily relied on DB
triggers. We created a new WO application called CheckInProcessor. It
listened on a port for new data (using a proprietary protocol). The
external app that used to write new data directly to the DB was changed
to send the data to the CheckInProcessor. The CheckInProcessor writes
that new data to the DB, performs tasks equivalent to the old triggers,
and notified the other WO apps of any changes (using WONDER's
EOUpdateNotification framework).
Christian
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden