Subject | Re: [firebird-support] Bad design causing problems |
---|---|
Author | Nando Dessena |
Post date | 2006-05-24T18:05:13Z |
Rik,
R> Even though someone advised me against it, the inserts are being done using
R> a selectable stored procedure.
you can easily turn it into an executable stored procedure, run it
through "EXECUTE PROCEDURE" instead of "SELECT FROM", thus gaining a)
more portability among different database engines, and b) less
reprimands from folks here. :-)
R> I could make all the fields in the table unique, but then I'd have to trap
R> for the error and I haven't found how to do that in a stored procedure
R> yet.
have a look at WHEN; you can find examples in the stored procedures of
the employee sample database.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================
R> Even though someone advised me against it, the inserts are being done using
R> a selectable stored procedure.
you can easily turn it into an executable stored procedure, run it
through "EXECUTE PROCEDURE" instead of "SELECT FROM", thus gaining a)
more portability among different database engines, and b) less
reprimands from folks here. :-)
R> I could make all the fields in the table unique, but then I'd have to trap
R> for the error and I haven't found how to do that in a stored procedure
R> yet.
have a look at WHEN; you can find examples in the stored procedures of
the employee sample database.
Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================