Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Bugs & Issues> Loading basic selfservice object
 

Pages: 1 2
Bugs & Issues
Loading basic selfservice object
Page:2/2 

  Print all messages in this thread  
Poster Message
Jamanga
User



Location:
Sydney, Australia
Joined on:
21-Jul-2006 03:47:18
Posted:
91 posts
# Posted on: 05-Nov-2007 23:23:48.  
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!! Confused

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.. Laugh
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37830 posts
# Posted on: 06-Nov-2007 11:13:08.  
Thanks for doing this testing! Regular Smiley

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


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
kerpal
User



Location:

Joined on:
16-May-2008 07:32:34
Posted:
14 posts
# Posted on: 19-May-2008 10:35:17.  
Was there ever a resolution to this?

I'm experiencing a similar issue.
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37830 posts
# Posted on: 19-May-2008 13:47:30.  
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. Regular Smiley (we're not aware of any fix from their side)


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
Jamanga
User



Location:
Sydney, Australia
Joined on:
21-Jul-2006 03:47:18
Posted:
91 posts
# Posted on: 20-May-2008 01:56:34.  
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? Confused

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.
  Top
kerpal
User



Location:

Joined on:
16-May-2008 07:32:34
Posted:
14 posts
# Posted on: 20-May-2008 03:43:36.  
Hi Jamanga,

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

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!


  Top
Pages: 1 2  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.