Subject | RE: [Firebird-Java] Re: JayBird: Problems with Prepared Statements |
---|---|
Author | Rick Debay |
Post date | 2005-09-06T21:38:18Z |
Bad pseudo code...
statementExecutor(String sql)
{
ps = prepare(sql);
statementExecutor(ps);
}
statementExecutor(PreparedStatement ps)
{
ps.executeQuery()
}
-----Original Message-----
From: Firebird-Java@yahoogroups.com
[mailto:Firebird-Java@yahoogroups.com] On Behalf Of pifproject
Sent: Tuesday, September 06, 2005 1:48 PM
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] Re: JayBird: Problems with Prepared Statements
Hello Rick,
thanks for your replies!
or/after the other, it's because of supporting both types with a single
'statementExecutor()' method.
but how can you pass a prepared statement to the statementPreparer()
method, when you cannot convert this very prepared statement to String?
vendor-specific due to standardization concerns seems quite reasonable.
I have asked for the described feature in order to be able to provide a
more general-purpose solution, which will be nice for the end users.
- Roman wrote:
http://sourceforge.net/tracker/index.php?func=detail&aid=1283213&group_i
d=130139&atid=718321
------------------------ Yahoo! Groups Sponsor --------------------~-->
Fair play? Video games influencing politics. Click and talk back!
http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/saFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
statementExecutor(String sql)
{
ps = prepare(sql);
statementExecutor(ps);
}
statementExecutor(PreparedStatement ps)
{
ps.executeQuery()
}
-----Original Message-----
From: Firebird-Java@yahoogroups.com
[mailto:Firebird-Java@yahoogroups.com] On Behalf Of pifproject
Sent: Tuesday, September 06, 2005 1:48 PM
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] Re: JayBird: Problems with Prepared Statements
Hello Rick,
thanks for your replies!
> In order to support executing unprepared SQL, prepared statements areKind of. It's not because of supporting one type of SQL statements
> converted to a String so both prepared and "free-form" SQL gets passed
> to statementExecutor(String sqlStatement)
or/after the other, it's because of supporting both types with a single
'statementExecutor()' method.
> What if instead all Strings get prepared bystatementPreparer(String sqlStatement)
> and then both types of statements just get executedWell that's somehow an improvement suggestion for the SQL execution:
but how can you pass a prepared statement to the statementPreparer()
method, when you cannot convert this very prepared statement to String?
> I vote for keeping it vendor specific. I access all vendor stuffAs I have mentioned in my previous reply, the idea for solving it
> within wrappers anyway
vendor-specific due to standardization concerns seems quite reasonable.
I have asked for the described feature in order to be able to provide a
more general-purpose solution, which will be nice for the end users.
- Roman wrote:
> > Please fill the feature request at SourceForge.net, so we do not- me:
> > forget it before the next RC and/or final release.
> > Just type few words - Yahoo might decide to remove their message
> > database.
> Okay, I'll try to formulate something as a description.Here it is:
http://sourceforge.net/tracker/index.php?func=detail&aid=1283213&group_i
d=130139&atid=718321
------------------------ Yahoo! Groups Sponsor --------------------~-->
Fair play? Video games influencing politics. Click and talk back!
http://us.click.yahoo.com/T8sf5C/tzNLAA/TtwFAA/saFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links