Subject | [IBO] SOUNDEX with IBOQuery |
---|---|
Author | Gerald W. McCaig - Efi Soft |
Post date | 2002-06-18T14:07Z |
Can anyone tell me the syntax for using the SOUNDEX feature with the
IBOQuery. I would like to incorporate it in a where statement.
Thanks,
Jerry
-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: Tuesday, June 18, 2002 7:29 AM
To: IBObjects@yahoogroups.com
Subject: Re: [IBO] Re: Building a statement at runtime
At 10:52 AM 18-06-02 +0000, you wrote:
You simply CANNOT do this. In IB/FB, stored procedures are validated
and
compiled at create time, never at run-time. Thus, you cannot use
variables
to represent either elements of an SQL statement nor metadata objects,
because the compiler needs to know and validate the metadata before it
will
compile your procedure. Variables can be *only* constants representing
data.
Bad luck. You will have to find another way to construct these run-time
statements and you must do them in your client application.
regards,
Helen
All for Open and Open for All
Firebird Open SQL Database . http://firebirdsql.org .
http://users.tpg.com.au/helebor/
_______________________________________________________
________________________________________________________________________
___
IB Objects - direct, complete, custom connectivity to Firebird or
InterBase
without the need for BDE, ODBC or any other layer.
________________________________________________________________________
___
http://www.ibobjects.com - your IBO community resource for Tech Info
papers,
keyword-searchable FAQ, community code contributions and more !
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
IBOQuery. I would like to incorporate it in a where statement.
Thanks,
Jerry
-----Original Message-----
From: Helen Borrie [mailto:helebor@...]
Sent: Tuesday, June 18, 2002 7:29 AM
To: IBObjects@yahoogroups.com
Subject: Re: [IBO] Re: Building a statement at runtime
At 10:52 AM 18-06-02 +0000, you wrote:
>Ciao, lelePaolo,
>I try to explain better.
>I've created, in the sql explorer, a new procedure:
>CREATE PROCEDURE PROCEDURE1 AS
>declare variable C0 varchar(100);
>declare variable C1 varchar(100);
>declare variable C2 varchar(100);
>declare variable C3 varchar(100);
>declare variable C4 varchar(100);
>BEGIN
>C1 = 'INSERT INTO PIANIF(MINUTI, ';
>C2 = 'CLV2) ';
>C3 = 'VALUES(1, ';
>C4 = '"00003")';
>C0 = C1+C2+C3+C4;
>C0;
>END
>After clicking "Apply" the error message is:
>General SQL error
>Token unknown - line 13, char 1
>;
>=============================
>In IB_WISQL the error is:
>------------------
>Page Error message
>ISC ERROR CODE:335544569
>
>ISC ERROR MESSAGE:
>Dynamic SQL Error
>SQL error code = -104
>Token unknown - line 13, char 1
>;
>
>STATEMENT:
>TIB_DSQL: "frmDSQL.dsqlEdit"
>------------------
>Page SQL message
>SQL ERROR CODE:-104
>
>SQL ERROR MESSAGE:
>Invalid token
>=============================
You simply CANNOT do this. In IB/FB, stored procedures are validated
and
compiled at create time, never at run-time. Thus, you cannot use
variables
to represent either elements of an SQL statement nor metadata objects,
because the compiler needs to know and validate the metadata before it
will
compile your procedure. Variables can be *only* constants representing
data.
Bad luck. You will have to find another way to construct these run-time
statements and you must do them in your client application.
regards,
Helen
All for Open and Open for All
Firebird Open SQL Database . http://firebirdsql.org .
http://users.tpg.com.au/helebor/
_______________________________________________________
________________________________________________________________________
___
IB Objects - direct, complete, custom connectivity to Firebird or
InterBase
without the need for BDE, ODBC or any other layer.
________________________________________________________________________
___
http://www.ibobjects.com - your IBO community resource for Tech Info
papers,
keyword-searchable FAQ, community code contributions and more !
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/