At 09:27 PM 2/04/2008, you wrote: > >> Of course you do! Consider the logic of updating a record that is >> being deleted! >I thought BEFORE delete is exactly as it say, before deletion, and the >record exists and I can use of it and operate as I want!
Think about it. A trigger belongs to an OPERATION and an EVENT. You cannot convert a DELETE OPERATION into an UPDATE OPERATION. Once you have posted the delete, the only thing that is going to happen to that record is deletion. So, the record itself is read-only: this means that you can READ values from it during a trigger event but you cannot WRITE values to it. >This is possible in 1.5! No, it isn't. It's a no-op in Fb 1.5. The difference now is that the engine *tells* you about it so that you can repair your code. >In this case if I delete a record I can't modify anything on that record! Of course not. A deleted record is, well, DELETED. If you want to modify the record, then use UPDATE, not DELETE! ;-) >The migration FB 2.X will be very difficult! This thread has become totally off topic for the net-provider forum but I must say I'm curious to know what you thought you were achieving when you believed you were able to modify a record during deletion... Also, would you fix your email client/spam filtering so it doesn't mess around with the message Subject, please? If you don't know how, at least edit the Subject before you send. Helen ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
