Hi, i need some assistance in choosing an ADO.NET- provider for MySQL.
We will port an app from Visual Objects to C# soon. Currently we are using the C-API. Our tables are mainly innoDB and we use transactions. We will use relations. Most of our customers have - 5-20 concurrent users - the server running on a machine not reserved for MySQL For one customer we are thinking to use MSSQL or Oracle. Therefore the provider should be exchangeably with low spends. Should we perhaps choose a non-native-provider? Till now we only used client-side cursors and small (one-)record- sets. Should we use server-side ones. Are there any ADO.NET- specific considerations i should make about cursors different from those when using the API? Thanks in advance, TomH -- PROSOFT EDV-Loesungen GmbH & Co. KG phone: +49 941 / 78 88 7 - 121 Ladehofstrasse 28, D-93049 Regensburg cellphone: +49 174 / 41 94 97 0 Geschaeftsfuehrer: Axel-Wilhelm Wegmann [EMAIL PROTECTED] AG Regensburg HRA 6608 USt.183/68311 http://www.proSoft-Edv.de -- -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
