On Apr 24, 2:43 am, Gary Doades <[email protected]> wrote:
> On 24/04/2010 10:03 AM, Gary Doades wrote:
>
>
>
> > OK, I've poked around a bit by using a trace on a SQL Server backend.
>
> > The fundamental issue appears to be the Sequel (via whatever means) is
> > getting a new connection for EVERY statement issued to the server.
> > This is obviously BAD, and not just for transactions. Temporary tables
> > which persist and are visible only for a connection would fail
> > miserably too. Probably a few other things.....

Yes.  This is what I meant by not a consistent connection object.

> > I'll try some more tests when I get the chance to see if I can nail it
> > down further. If it can't be fixed then it should probably be dumped
> > as I suspect that people will run into may problems and not just with
> > transactions. As a minimum there should be a big warning in the docs
> > that various operations may fail.

I don't plan on dumping it, as it works fine for read only workloads.
I actually use it in production for a read only reporting program.

> Sorted!!
>
> You need to use a different provider. I use SQLNCLI10 to connect to both
> SQL Server 2008 and SQL Server 2000 and it all works OK. That's also why
> I hadn't seen any problems.
>
> An example uri:
>
> ado://sa:test...@localhost/test?provider=SQLNCLI10
>
> an example conn_string:
>
> Provider=SQLNCLI10;Uid=sa;Pwd=testing;Database=test;Server=localhost
>
> I'm not sure what the default provider is if you don't explicit ask for
> one, but it's broken :(

If you don't specify one, Sequel doesn't specify one, so it probably
uses whatever the win32ole default is.  It's not Sequel's fault that
win32ole's default is broken.

> Maybe a switch to SQLNCLI10 as the default provider? If it's not already
> installed, it's a free download from Microsoft.

I'll test this and see what happens if it isn't available.  If I can
make it the default without breaking anything, then I will.

Thanks for doing the research and figuring this out.

Jeremy

-- 
You received this message because you are subscribed to the Google Groups 
"sequel-talk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sequel-talk?hl=en.

Reply via email to