> 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 thoug
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
At 09:07 PM 2/04/2008, you wrote:
>> Then your Before Delete trigger probably has a reference to
>> NEW.something. It is invalid in a delete trigger.
>Trigger ddl is:
>
>CREATE OR ALTER TRIGGER RPL_doc_invoice_BDEL FOR doc_invoice
>ACTIVE BEFORE DELETE POSITION 1000
>as
> declare variable v_rep
At 11:29 PM 1/04/2008, Mercea Paul wrote:
>Using FB 1.5.5 SS , FB.Net provider 2.5, VS C#2005.
>
>Database created with FB 1.5.3, ODS 10.1, Dialect 1.
>
>I have a SP which is running fine like execute procedure
>balance(@p1,@p2,@p3);
>
>The same database, but under FB 2.1 RC2 (17755), running s
First try 2.1 FirebirdClient. The 2.5 has still unfinished work on 2.1
protocol changes. This can cause problems.
> If (exists(select 1 from table2 t2 where t2.id= :v_a and t2.v=:v_b)) then
Isn't this IF redundant? ;)
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.vyvojar.cz/jirka/ | htt
Hi
Using FB 1.5.5 SS , FB.Net provider 2.5, VS C#2005.
Database created with FB 1.5.3, ODS 10.1, Dialect 1.
I have a SP which is running fine like "execute procedure
balance(@p1,@p2,@p3);"
The same database, but under FB 2.1 RC2 (17755), running same SP I get this
error:
base {System.Data.Common
