Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
Simple tests: MyODBC and VS.NET '05

Simple tests: MyODBC and VS.NET '05

2006-05-03       - By David Dindorp

 Back
Hello.

Here is a couple of simple tests using
MyODBC v3.51.12-2 and Visual Studio .NET 2005.

I'm hoping that the MyODBC dev team can perform
these (should take about 20 minutes) before doing
the next release of MyODBC.  Alternatively, the
dev team can post a prerelease on this list and
I'm sure that someone will step up to the task.

I haven't pursued any of the problems I've found further than
mentioned here, mainly because tracing and other things are
currently known to be broken in MyODBC.


1) Start by creating a new Windows Forms project
===============================================Open these snap-ins:
Server Explorer (Menu:  View --> Server Explorer)
Data Sources (Menu:  Data --> Show Data Sources)


2) Create data source (Server Explorer)
======================================Using DSN:
Driver={MySQL ODBC 3.51 Driver};
Server=<ip_address>;Uid=<user>;Pwd=<password>

Seems to work fine, "Test Connection" succeeds.

When examining the created object the DSN looks like this:
Driver={MySQL ODBC 3.51 Driver};
option=0;port=0;server=<ip_address>;uid=<user>

Note the bogus 'port' option.


3) Browse tables (Server Explorer)
=================================To connect, right-click data source and choose
'Refresh'.
Does not work, an error dialog pops up:
-- ---- ---- ---- ---- ----
Server Explorer Error
-- ---- ---- ---- ---- ----
Server Explorer is unable to perform this operation.
See below for details:

Failed to call the ODBC driver connection utility.
-- ---- ---- ---- ---- ----
OK
-- ---- ---- ---- ---- ----


4) Add data source to project (Data Sources)
===========================================Does not work.
An error dialog pops up:
-- ---- ---- ---- ---- ----
Microsoft Visual Studio
-- ---- ---- ---- ---- ----
Failed to open a connection to the database

"Failed to call the ODBC driver connection utility."

Check the connection and try again.
-- ---- ---- ---- ---- ----
OK   Help
-- ---- ---- ---- ---- ----


5) Create a new data source with altered DSN (Server Explorer)
=============================================================Trying to add a
new DSN that includes a 'Port' setting.

Does not work, VS.NET 2005 deletes the new data source automatically
if the transport (ODBC) and user name (password?) matches an existing
data source.


6) Create new data source by replacing old (Server Explorer)
===========================================================Removed the old data
source and created a new
one where the DSN contains "Port306;".

Works.


7) Repeat test 3 - Browse tables (Server Explorer)
=================================================To connect, right-click the
data source and choose 'Refresh'.

Connection succeeds, right-click data source and choose 'Properties'
to see MySQL server version number in 'Version' property.

Browsing tables does not work, VS.NET 2005 cannot see any tables.


8) Repeat test 4 - Add data source to project (Data Sources)
===========================================================Fails.  An error
dialog is shown:
-- ---- ---- ---- ---- ----
Data Source Configuration Wizard
-- ---- ---- ---- ---- ----
Which database objects do you want in your dataset?

An error occurred while retrieving the information from the database.

Attempted to read or write protected memory. This is often an
indication that other memory is corrupt.

DataSet name:
-- ---- ---- ---- ---- ----
< Previous   Next >   Finish   Cancel
-- ---- ---- ---- ---- ----


9) Query window (Server Explorer)
================================Right-click data source, choose 'New Query'.

Works, but error dialog pops up:
-- ---- ---- ---- ---- ----
Microsoft Visual Studio
-- ---- ---- ---- ---- ----
Attempted to read or write protected memory. This is often an
indication that other memory is corrupt.
-- ---- ---- ---- ---- ----
OK
-- ---- ---- ---- ---- ----


10) Perform SQL query (Query window)
===================================Using this query (and Menu: Query Designer -
-> Execute SQL to run):
SELECT * FROM <database>.<table>

Works.


11) Create a new ASP.NET Web Site project
========================================Open the Toolbox snap-in (Menu:  View -
-> Toolbox) and make sure it
shows non-visible controls (Menu:  View --> Non Visual Controls).

Open the default web page in design view by right-clicking
"default.aspx" and choosing 'View Designer'.


12) Add data source to a project
===============================Drag an 'SqlDataSource' from the Toolbox to the
Designer view.

Click the tiny 'Tasks' button on the newly created object and choose
'Configure Data Source'.

Does not work; after selecting connection, an error dialog pops up:
-- ---- ---- ---- ---- ----
Microsoft Visual Studio
-- ---- ---- ---- ---- ----
Database schema could not be retrieved for this connection.

Please make sure the connection settings are correct and that
the database is online.

Attempted to read or write protected memory. This is often an
indication that other memory is corrupt.
-- ---- ---- ---- ---- ----
OK
-- ---- ---- ---- ---- ----


13) Other notable MyODBC <-> .NET interaction issues
===================================================Cannot use DOUBLE fields
(probably other floating point fields too).
http://bugs.mysql.com/5225

Cannot use BIGINT fields.
http://bugs.mysql.com/18755


--
MySQL ODBC Mailing List
For list archives: http://lists.mysql.com/myodbc
To unsubscribe:    http://lists.mysql.com/myodbc?unsub=mysql@(protected)