Re: Stored proc returning result set (and output params) with MS SQL server

2008-04-21 Thread Andrus Adamchik
Then I didn't understand your question... In my test cases, using a manual transaction would prevent an exception and I could read the out parameters without a problem, even on error conditions. Andrus On Apr 21, 2008, at 6:20 PM, Marc Gabriel-Willem wrote: Hi Andrus, We are using intensi

RE: Stored proc returning result set (and output params) with MS SQL server

2008-04-21 Thread Marc Gabriel-Willem
Hi Andrus, We are using intensively the QueryResponse ;) Here is the problem; the call of the 'performGenericQuery' method throws an exception. So we don't have any chance to use the QueryResponse! Even if the stored proc does not return any 'result set' in that error situation, we need to be a

Re: Stored proc returning result set (and output params) with MS SQL server

2008-04-21 Thread Andrus Adamchik
QueryResponse is the most generic response that you can get out of Cayenne, designed to incorporate multiple results sets, update counts, and surely - stored procedure out values. The OUT values are returned as the first "resultList". So you can do something like this: if(result.next()) {

RE: Stored proc returning result set (and output params) with MS SQL server

2008-04-21 Thread Marc Gabriel-Willem
Hello, Thank you for your investigation. Your workaround solves partially the problem. It is a good think that we can 'commit' or 'rollback' the transaction ourself. But it remains a major problem regarding the QueryResponse returned by the 'performGenericQuery' method. Our low level layer requi

RE: Mysql and usernames

2008-04-21 Thread Ozakca, Muzaffer
Andrus and Kevin, You were both right, it was some kind of reverse lookup issue on the Mysql side that prevents logging in. I was confused about that and adding the IP address to the Mysql user resolved the issue. Thanks, Muzaffer > -Original Message- > From: Andrus Adamchik [mailto:[E