Is there a bug in 3.5 using joins?

Mailing List

Home

Forum Home

MySQL General - General MySQL discussion

MaxDB - Everything about MaxDB, formerly known as SAP DB

MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP

MySQL++ - Programming with the C++ API to MySQL

ODBC - ODBC with the MySQL Connector/ODBC driver

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()

Is there a bug in 3.5 using joins?

Is there a bug in 3.5 using joins?

2005-06-04 - By Billy Yard

Back
When I use a join with a search that returns a null value, I get an error
message "invalid field size".
The same join returns an empty set with the MySQL monitor.

Earn $52 per hosting referral at Lunarpages.