Hi

Interesting ...

The argument usually used by people looking for 

- triggers
- functions + procedures
- foriegn keys

is the persuit of data integrity, and encapsulating business logic within the 
database.

Whilst this goal is noble, it can be fully achieved within the application 
code, and not in the database. Having this functionality within the 
application has the following advantages

- database design is simpler
- database load is lower
- fewer locking problems
- testing data at application level is cleaner and more efficent than at the 
database.

Any argument that implementing the implementing business logic ONCE at this 
database is more efficient ignores the use of 3GL libraries.

I have worked on many projects with Oracle and MySQL, and I have always found 
implmenting business logic within the application more efficient. This does 
not mean triggers and procedures where not used, but complicating business 
logic that might cause a cascade of updates, inserts and deletes from many 
sources is always problematic.

As MySQL stands now, I would recommend running a daemon process, written in 
Perl (or other language), that could process new data. This has the advantage 
of being future proof, and eliminates the potential problems that triggers 
cause due to data inserts from multiple sources.

Simple create two table sets, one for loading data, and one for processed 
data. Have a perl daemon scan the load tables every 30s and process the data 
accordingly.  


All the best

Simon


On Tuesday 17 June 2003 21:48, Jeff Mathis wrote:
> the main reason I might suggest NOT to do this is a data integrity one.
> As long as someone can go in through a mysql prompt and touch data, PHP
> or ASP will do you no good.
>
> Data integrity checks should, in so far as possible, always be put into
> the schema, and not in an API.
>
> just my two cents ....
>
> Primaria Falticeni wrote:
> > Why don't you use PHP or ASP functions on the server-side in Web page
> > code. They act like a trigger and you don't need MySQL 5.0 for them.
> > Remember that you can benefit from the both servers: MySQL and Web
> > server.
> >
> > ----- Original Message -----
> > From: "Kerry Colligan" <[EMAIL PROTECTED]>
> > To: <>
> > Sent: Tuesday, June 17, 2003 9:10 PM
> > Subject: Triggers
> >
> > > I see that 5.x will support triggers. Does anyone have any advice for
> > > implementation of triggers on the DB? I will need to be able to utilize
> >
> > them
> >
> > > from web applications AND from command-line type interface. Any
> >
> > suggestions
> >
> > > welcome at this point. (RH 7.3, MySQL 3.23.56 presently)
> > >
> > > Thanks
> > >
> > > --
> > > Kerry
> > >
> > >
> > >
> > > --
> > > MySQL General Mailing List
> > > For list archives: http://lists.mysql.com/mysql
> > > To unsubscribe:
> >
> > http://lists.mysql.com/[EMAIL PROTECTED]
> >
> > --
> > MySQL General Mailing List
> > For list archives: http://lists.mysql.com/mysql
> > To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]
>
> --
> Jeff Mathis, Ph.D.                    505-955-1434
> The Prediction Company                        [EMAIL PROTECTED]
> 525 Camino de los Marquez, Ste 6      http://www.predict.com
> Santa Fe, NM 87505

-- 
Simon Windsor

Tel: 01454617689
Mob: 07720 447385
Email: [EMAIL PROTECTED]

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to