mysql help me! SOS

zhuningwll · 07-28-2006, 05:01 AM

now we update database(mysql4.0.17)to 4.1.18 we test seaprint machine .but in seaprint database we run ''select * from tl where tl='FC406056' it dislplay null in 'kd' field we see it 'null'

mdarby · 07-28-2006, 06:01 AM

So you have a database named 'tl' with a table named 'tl', and then a field named 'tl'?

Are you asking why 'null' is showing up when there is nothing stored in the field 'kd'?

zhuningwll · 07-28-2006, 06:05 AM

Quote:

Originally Posted by mdarby

So you have a database named 'tl' with a table named 'tl', and then a field named 'tl'?

Are you asking why 'null' is showing up when there is nothing stored in the field 'kd'?

yes!!!!!!!!!!!!

Marsanghas · 07-28-2006, 06:51 AM

Maybe because there's no data in the kd field???

I think I don't understand the question... the query has nothing to do with the question....

mdarby · 07-29-2006, 08:01 AM

And your naming conventions is really confusing. It will trip up people down the road. I'm amazed that MySQL even returns anything on that query.

Slim Backwater · 07-29-2006, 09:01 AM

Quote:

Originally Posted by zhuningwll

now we update database(mysql4.0.17)to 4.1.18 we test seaprint machine .but in seaprint database we run ''select * from tl where tl='FC406056' it dislplay null in 'kd' field we see it 'null'

My guess is that he's saying that with 4.0.17, null value fields didn't display the text 'null', and after the upgrade to 4.1.18, a null value field displays the text 'null'.

So I think he's looking for a way to suppress the 'null' text from appearing in the result set.

*edit: Several visible behaviors have changed between MySQL 4.0 and MySQL 4.1 to fix some critical bugs and make MySQL more compatible with standard SQL. These changes may affect your applications. http://dev.mysql.com/doc/refman/4.1/...-from-4-0.html