Is NPGSQL stable and secure as ODBC driver?

[Stefano Ravagni]

Hello, i'm new in Npgsql and i would to pass from ODBC connection provided by Postgresql.org to Npgsl...

...but i have one only question because i have to change in a work location...so it's delicate situation where i wannot loss data or other...

Is Npgsql stable, secure and without problem ? Is competitive respect to original ODBC driver ?

Could i use with the same SQL query?

Which problem i have to count ?

Thanks!
 

[Francisco Figueiredo Jr.]

Hi!

Npgsql 2.0.x series are stable enough to be used on production. We are finalizing 2.1 version.

I never used the ODBC driver so I can't compare. :(

There are still many bugs in Npgsql but I think that for 90% of Npgsql users, it works without any problem. We are missing some corner cases, like https://github.com/npgsql/Npgsql/pull/164 and others big ones like DDEX support but it is nothing that would prevent you from using it. We also have a lot of support for EF6 but we are working on more features, like https://github.com/npgsql/Npgsql/pull/91.

I think that ODBC uses question marks (?) to indicate parameters in queries. If you are using them, you will need to change to @parameter or :parameter format which Npgsql uses.

The problems you may face depend on your usage. If you are going to use Entity Framework you may expect some problems. If you are using simple queries with parameters, you will be ok.

Please, give it a try and let us know if you have any problems. We try to fix all the bugs reported and we are very supportive.

I hope it helps.

[Stefano Ravagni]

Thanks tor replay...
I use normal sql query, sometimes with subquery but no others... i usually make query wich can be considered universally for all major database i support in my work.

Think you could i abandon odbc TO npgsql in this case?

[Francisco Figueiredo Jr.]

In this case I think you won't have problems using Npgsql. 

ODBC is a very good library and if you are already using it and you are comfortable with it, I think you should keep using it.

I think the only good reason for you to drop ODBC and use Npgsql is if ODBC is giving you problems.

Another point is the client configuration. Npgsql was built from the ground up to not depend on external native libraries so it may be easier to configure and deploy than ODBC.

I hope my explanation helps you. If you need more info, please, let us know. I'll be glad to help.

[Stefano Ravagni]

Yes, i would abbandona odbc because of difficult deployment for my client setup... with npgsql, which id stand-alone library, i have compact distribution...
... but i hope it run fast and stable as Odbc...

[Stefano Ravagni]

Today i tryed npgsql 2.0.12

I obtain many error respect to ODBC connection type...

In particular, when use ExecuteReader on datareader, after pass datareader to a datasource, if i check DataReader.HasRow give me a FALSE result.... in other provider not happen...

I cannot dispose npgsql connection and re-open because after that i obtain an error relative to npgsql connection disposed...

I think is so delicate ...for example, no problem with MySQL.dll library ...

Could i hope in future release ??