Ok, I checked bugs.mysql.net and it does appear to have been found, and
the bug in question trampled into a million pieces.
I bk'ed the main source tree, compiled, tested, and it works like a charm.
Still looking forward to Beta 2 though! ;)
-------- Original Message --------
Subject: Odd ?bug? with DBNull Values
Date: Tue, 28 Sep 2004 15:08:07 +0100
From: Barry Zubel <barry@stripped>
A quick question to see if this has been noticed before.
I'm populating a datatable direct from a MySql database via the 1.0.0
Code is similar to the following:
-- BEGIN CODE BLOCK --
dim sSql as string = "SELECT JOB_NO, ORDVAL, REQD FROM S_MASTER"
dim conn as new MySqlConnection(mainApp.mysql.connectionstring)
dim comm as new MySqlCommand(sSql, conn)
dim rs as new MySqlDataAdapter(comm)
dim dt as new Datatable
grdData.Datasource = dt
-- END CODE BLOCK--
grdData is a DataGrid, and displays the results perfectly... in most cases.
The case that I've come across is when you hit a DBNull value in one of
the fields in the DataTable. I initially noticed that all the remaining
fields in that column in the DataGrid were also null. Upon inspection
of the DataTable object itself, it appears that the fields in the table
are also null. When running the exact same parameter directly through
PhpMyAdmin, results are displayed for those fields in the rows that are
Is this an issue with the connector? I've highly-simplified the code in
this email, but I'm about to go set up a clean-room test case and see if
it still happens.
Anyway - still looking forward to the next beta release, Reggie! ;)
MySQL on .NET Mailing List
For list archives: http://lists.mysql.com/dotnet
To unsubscribe: http://lists.mysql.com/dotnet?unsub=1