Hi Frans

I can confirm that there is an ASE driver buggo with regard to their DataReader.

CommandBehavior.SingleRow does NOT return a value, and of course when querying by an existing PK - it really should!!

CommandBehavior.SingleResult or CommandBehavior.Default did return data. I'll forward this issue to Sybase.

Thanks for all your debugging + time. I think I'll do my demo app in MSSQL..

Thanks for doing this testing!

I'm sorry Sybase dropped the ball this big... I hope they'll fix it soon.

Was there ever a resolution to this?

I'm experiencing a similar issue.

kerpal wrote:

Was there ever a resolution to this?

I'm experiencing a similar issue.

If you're using their latest ado.net provider, the answer is no. (we're not aware of any fix from their side)

Hi,

I can report this issue is still there when using the most current drivers, as per: http://search.sybase.com/kbx/changerequests?bug_id=485824

Coincidentally a Sybase support engineer called yesterday to ask if they could close my case report. He gave me the link above, and informed me that this issue is not in their Development teams list of priorities, so he's no idea when it might be fixed.

I understand priorites, but this problem: * has been outstanding for over 6 months now * is a software regression (which indicates they probably aren't using automated unit-tests on their drivers, which, time allowing, I couldn't imagine developing a driver without) * is a very small-risk patch from Sybase's point of view. i.e. as a minimum, rather than ignoring the calls to CommandBehaviour.SingleRow, I suspect it will simply be a matter of pointing to the CommandBehaviour.SingleResult logic, which seems to work fine from my testing. * is generating bad Sybase PR

Interesting business decision?

Please correct me if I'm wrong, but I'm assuming the workaround is to purchase LLBLGen - which gives you access to the source code. Then replace any references to CommandBehaviour.SingleRow with CommandBehaviour.SingleResult within the relevant solution, rebuild the assemblies and add these to the GAC, replacing the existing ones. You'll need to repeat this process for each subsequent LLBLGen release, until Sybase fix the bug.

Hi Jamanga,

Nice to have someone else on this forum in the same timezone as me

This really is pretty shoddy stuff from Sybase. I didn't realise that we got access to the source code for LLBL Gen ... Thanks for your suggestion ... I'll look into it.

[Edit] Your suggestion worked great ... Thanks!