Re: SELECT from TEXT column returns undef

Benjamin Schuster-Boeckler <[email protected]> Thu, 10 Sep 2009 15:02:02 +0200
Newsgroups gmane.comp.db.mysql.perl
Message-ID <[email protected]>
Just to clarify: I did of course compile DBD::mysql in 64bit against =20
the 5.4.1 libraries. This was the main reason I moved to 5.4.1 in the =20=

first place: I couldn't compile 64bit DBD::mysql to run with 64bit =20
perl without having a 64bit mysql, hence the move to 5.4.1 beta.

I have no problems querying the database, the only issue I have is =20
that clearly somewhere there is a package maximum size set, which =20
causes TEXT columns of certain length to return undef.

Also not that I DID set max_allowed_packet =3D 32M in my.cnf. Any other =20=

place where the problem might stem from?

Ben

On 10 Sep 2009, at 14:51, Yair Lapin wrote:

> You must upgrade also your drivers DBD::mysql and check that you =20
> have installed the correct mysqlclient libraries for the version =20
> 5.4.1. Another thing, check the mysql libraries; if they are 64bit =20
> and your perl must be also 64 bit else you have a problem. You can't =20=

> compile 64bit libraries with into perl 32bit.
> This is the reason I don't upgrade mysql, I prefer to throw the =20
> machine and build new one from the beginning. You must rebuild all =20
> the drivers, PHP also.
>
> -----Original Message-----
> From: Benjamin Schuster-Boeckler [mailto:[email protected]]
> Sent: Thursday, September 10, 2009 2:53 PM
> To: [email protected]
> Subject: SELECT from TEXT column returns undef
>
> I recently upgraded to mysql 5.4.1-beta 64bit running on Snow Leopard,
> with perl5.10.0 and DBD::mysql 4.012.
>
> Since the upgrade, SELECTs from a MEDIUMTEXT column return undef. I
> get the impression this is because some size limit is exceeded (the
> return value should be < 30000 characters). This used to work happily
> before, so I'm wondering where I find any settings to fix this? Funny
> enough, I can run the queries successfully in Sequel (a mysql admin
> app for mac). Makes me think the problem must be somewhere in the
> client connection library. Any help would be greatly appreciated!
>
> Best,
> Benjamin
>
> --
> MySQL Perl Mailing List
> For list archives: http://lists.mysql.com/perl
> To unsubscribe:    =
http://lists.mysql.com/[email protected]

--
Benjamin Schuster-B=F6ckler
Frundsbergstrasse 23a
82064 Strasslach
Deutschland



-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/[email protected]