Hi Jeremy,
We are using JDBC:MSSQL driver and I realise there's a similar question
posted here at StackOverflow
<https://dba.stackexchange.com/questions/44372/is-there-any-way-to-retrieve-messages-in-sql-server-through-jdbc>
:
I think the way it's getting it from JDBC is thru Statement.getWarnings()
like this:
Statement stmt = ...;
stmt.execute("some_procedure");
SQLWarning warning = stmt.getWarnings();
while (warning != null){
System.out.println(warning.getMessage());
warning = warning.getNextWarning();}
I am not sure if there's an equivalent method in Sequel that we can use in
order to implement capturing of this warning message. In my application, I
am using "fetch" command which returns single "result_set" all the time.
Additional question I have is that is there a way to detect presence of
multiple result set?
Thank you so much for your reply.
Regards,
elmer
On Monday, 4 June 2018 11:26:03 UTC+10, Jeremy Evans wrote:
>
> On Sunday, June 3, 2018 at 5:40:57 PM UTC-7, ELMER IBAYAN wrote:
>>
>> Hi Jeremy,
>>
>> Thank you for your reply. I really appreciate the help that your team can
>> extend.
>> Maybe I didn't really explain in detail what I need. I would like to grab
>> the whole message returned when calling a stored procedure which shows up
>> in the Message Tab in T-SQL/SQL Server output which typically would log
>> something similar below:
>>
>> *Msg 8134, Level 16, State 1, Line 56*
>> *Divide by zero error encountered.*
>>
>> If I wanted to capture whatever message will be written, is there a
>> method from 'sequel gem' that I can use to grab the whole thing? Currently,
>> I am detecting the result set, if it contains return_code to be 0, then I
>> consider them as completed successfully. However, there are cases wherein,
>> it doesn't return an exception since the result set has return_code 0, but
>> there are error in the "messages" tab output.
>>
>> Any advice on approaching this problem would be very much appreciated.
>>
>
> First, you'll need to figure out how to get this information from the
> tiny_tds driver (or whatever driver you are using). If you are successful
> doing that, then report back here with how to do that, and I can probably
> help with getting access to the information with Sequel.
>
> Thanks,
> Jeremy
>
--
You received this message because you are subscribed to the Google Groups
"sequel-talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.