try this
select silly(#value#) from dual
I think it can work.
On 5/8/05, Wolf <[EMAIL PROTECTED]> wrote:
> Hi Clinton,
>
> Thanks for the response. I have tried this through raw JDBC :
> con = DriverManager.getConnection("jdbc:postgresql:wiki");
> stat = con
> When I turn on logging, there is no reference to anything in the
> portion of the insert statement and the costObjectId is always 0. I've tried
> to
> change from the primitive int to the object, but the value of costObjectId is
> null then.
No selectKey execution in the logs, this sounds fa
Hi Clinton,
I tried it with a Prepared statement :
Connection con = DriverManager.getConnection("jdbc:postgresql:wiki");
PreparedStatement stat = con.prepareStatement("select silly('foo')");
stat.execute();
and it did work. I'm confused now. I'm going through the SqlM
I'll take a look at that. Thanks a lot.
Gregg
On 5/7/05, Clinton Begin <[EMAIL PROTECTED]> wrote:
>
> Here's the cool thingyou can write your own DAO transaction
> implementation. I'm assuming you're using SQL Maps. If so, just copy the
> SQL Map transaction implementation from the DAO fr
OH! I missed the "pg" part of your subject line. :-) I thought it said PL/SQL.
The reason your JDBC test worked is that you used a normal statement. Try that with a PreparedStatement.
iBATIS uses PreparedStatements exclusively.
Clinton
On 5/7/05, Wolf <[EMAIL PROTECTED]> wrote:
Hi Clinton,
Hi Clinton,
Thanks for the response. I have tried this through raw JDBC :
con = DriverManager.getConnection("jdbc:postgresql:wiki");
stat = con.createStatement();
stat.executeQuery("select silly('foo')");
and that works as expected.
I am using the same jdbc driver on both occasions.
I did try
Try select silly(text) from dual.
Cheers,
Clinton
On 5/5/05, Wolf <[EMAIL PROTECTED]> wrote:
Hi folks,Thansk for SqlMap, it is making life easier. I am having a problemwithPL/pgSQL functions called from a . I can get around this by notusing the function, but wanted tocall this issue to atten
That should work. But I don't believe you've stated what the
problem actually is. What is happening? Is there an
exception? Is the costObjectId always being set to the same
value? Is the sequence being incremented? Is the call to
sqlMapClient.insert() returning the key propertly?
What's the
Do ALL of your SqlMap calls follow this pattern:
try {
sqlMap.startTransaction();
//...do work
sqlMap.commitTransaction();
} finally {
sqlMap.endTransaction();
}
Clinton
On 5/6/05, Rafiq, Adnan <[EMAIL PROTECTED]> wrote:
I am using a transaction manager type = JTA in my sql-map-config.xm
Here's the cool thingyou can write your own DAO transaction
implementation. I'm assuming you're using SQL Maps. If so,
just copy the SQL Map transaction implementation from the DAO framework
into your own package name. Then, add startBatch() and endBatch()
to the constructor and commit meth
You only get that if you call .forceCloseAll().
Cheers,
ClintonOn 5/4/05, Folashade Adeyosoye <[EMAIL PROTECTED]> wrote:
Is this a normal logger/system out output for iBatis DAODEBUG[2005-May-04 22:47:24] -jdbc.SimpleDataSource(SimpleDataSource.java:506) - SimpleDataSourceforcefully closed/remove
You can try both.
EXTERNAL, won't do anything with the transaction. Which in many
cases works just fine. With JTA set, iBATIS will manage the
connection as part of the global transaction.
Most people find EXTERNAL is the easier of the two to get working.
Cheers,
ClintonOn 5/6/05, Rafiq, Adnan
Awesome Nathan. Thanks so much for fixing that.
Clinton
On 5/4/05, Nathan Maves <[EMAIL PROTECTED]> wrote:
Team,I have restored the FAQ on one way to use the built in BLOB and CLOBCustom Type Handlers (CTH). I have also added a section near thebottom on the to common problems.- 86 length on the
...try just running queryForList to see what you get back. That will help you determine why you're getting multiple rows back.
Clinton
On 5/7/05, Brian Beaulieu <[EMAIL PROTECTED]> wrote:
I can not seem to get around this error:java.sql.SQLException: Error: executeQueryForObject returned too many
If you intend to receive more than one record you should use
queryForList. If you intend to only receive one record as a class then
you would use queryForObject. If you are using queryForObject and only
want one object back then your SQL query is returning more than one
result and will fail. You ne
I can not seem to get around this error:
java.sql.SQLException: Error: executeQueryForObject returned too many
results.
at
com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.executeQueryForO
bject(GeneralStatement.java:104)
at
com.ibatis.sqlmap.engine.impl.SqlMapExecutorDe
16 matches
Mail list logo