NexusDB Newsgroups

NexusDB Newsgroups (http://www.nexusdb.com/forums/index.php)
-   nexusdb.public.support.adoprovider (http://www.nexusdb.com/forums/forumdisplay.php?f=10)
-   -   waiting patiently (http://www.nexusdb.com/forums/showthread.php?t=17807)

David Guest 6th July 2013 08:10 AM

waiting patiently
 
I now can create a Web application in VS 2012 and deploy it to my web
server with a minimum of effort.

All I need now is a nice ADO.Net driver to talk to Nexusdb ... one that
is integrated with VS 2012...and is nice and fast and reliable ...

oh, boy.....


bkv 3rd October 2013 05:55 PM

Dear Nexus team,
What is a current status of ADO.Net provider?
In the past, we were trying to use it, but it was too slow and too buggy.
Due to that we are using ODBC provider right now.
So, the question is: something changed? Have we to try to use ADO.Net provider again or it is just a waste of time?

Thanks, Konstantin.

Eivind Bakkestuen [NDD] 3rd October 2013 06:44 PM

Re: waiting patiently
 
> What is a current status of ADO.Net provider?

We have put a fair amount of effort into bringing the provider up to
proper quality standards, fixing bugs and also some performance
enhancements. There will be an update released when this work is
finished; sorry I don't have an exact date yet.

--
Eivind Bakkestuen [NDD]

David Guest 11th November 2013 01:18 AM

Re: waiting patiently
 
On 10/3/2013 2:44 AM, Eivind Bakkestuen [NDD] wrote:
>> What is a current status of ADO.Net provider?

>
> We have put a fair amount of effort into bringing the provider up to
> proper quality standards, fixing bugs and also some performance
> enhancements. There will be an update released when this work is
> finished; sorry I don't have an exact date yet.
>

Anything to report at this date re the .net provider?

Thorsten Engler [NDA] 11th November 2013 12:34 PM

Re: waiting patiently
 
David Guest wrote:

> Anything to report at this date re the .net provider?


I've been trying to find out for some time now why in certain cases a message
sent sent by the managed part of the provider (sent with a single winsock
call), arrives (received with a single winsock call) at the native part of the
provider in the wrong order (e.g. a block of bytes that should be at the end
arrives at the start of the message). Obviously that's causing significant
problems, especially when using EF.NET (the larger the message, the more likely
the problem, and EF.NET loves to generate 1000 line+ queries for the simplest
things...)



David Guest 11th November 2013 09:26 PM

Re: waiting patiently
 
On 11/10/2013 8:34 PM, Thorsten Engler [NDA] wrote:
> David Guest wrote:
>
>> Anything to report at this date re the .net provider?

>
> I've been trying to find out for some time now why in certain cases a message
> sent sent by the managed part of the provider (sent with a single winsock
> call), arrives (received with a single winsock call) at the native part of the
> provider in the wrong order (e.g. a block of bytes that should be at the end
> arrives at the start of the message). Obviously that's causing significant
> problems, especially when using EF.NET (the larger the message, the more likely
> the problem, and EF.NET loves to generate 1000 line+ queries for the simplest
> things...)
>
>


thank you, Thorsten


All times are GMT +11. The time now is 07:43 AM.

Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.