duh

[dbsrgits/DBIx-Class.git] / t / 71mysql.t

diff --git a/t/71mysql.t b/t/71mysql.t
index 98f9a36..83f2a84 100644 (file)
--- a/t/71mysql.t
+++ b/t/71mysql.t
@@ -86,8 +86,9 @@ SKIP: {
 }
 
 ## Can we properly deal with the null search problem?
-
-use Data::Dump qw/dump/;
+##
+## Only way is to do a SET SQL_AUTO_IS_NULL = 0; on connect
+## But I'm not sure if we should do this or not (Ash, 2008/06/03)
 
 NULLINSEARCH: {
     
@@ -100,15 +101,16 @@ NULLINSEARCH: {
     ok my $artist2_rs = $schema->resultset('Artist')->search({artistid=>undef})
     => 'Created an artist resultset of undef';
     
-    is $artist2_rs->count, 0
-    => 'got no rows';
-    
+    TODO: {
+       $TODO = "need to fix the row count =1 when select * from table where pk IS NULL problem";
+           is $artist2_rs->count, 0
+           => 'got no rows';           
+    }
+
     my $artist = $artist2_rs->single;
     
     is $artist => undef
     => 'Nothing Found!';
-    
-    warn dump $artist->get_columns if $artist;
 }