On śro, 2005-01-26 at 10:42 -0600, Paul DuBois wrote: > On 1/26/05 8:19, "Wojciech Karlowski" <[EMAIL PROTECTED]> wrote: > > I am using Linux Debian (Sid) with libdbi-perl version 1.46-5 and mySQL > > version 4.1. Currently, I am trying to set up a perl script which will > > use the DBI module to connect to database. Everything works fine unless > > I try to insert large (around 18MB) text object. When I do this I get a > > following error: > > > > !! ERROR: 2020 'Got packet bigger than 'max_allowed_packet' > > > > I have already changed to settings for the "max_allowed_package" > > variable in the mysql server config (/etc/mysql/my.cnf) and in the local > > settings (~/.my.cnf) file. > > > > When I issue the same statement using the mysql client everything works > > w/o problems. > > > > Does someone know where can I set up the "max_allowed_package" variable > > for the DBI-driven connection? Obviously, it doesn't care about the > > server or client settings! > > > > Try this: > > Include the mysql_read_default_file or mysql_read_default_group option > in your DNS, and then put the max_allowed_packet setting in the appropriate > group. These options trigger calls to the mysql_options() C API function > and have the effect of telling mysql_real_connect() to read the option file > for options even when they're not available from the command line. >
Thanks for the tip. I have tried the modifiers you have mentioned in all combinations, but no luck - all the time I get the same error. Is it possible that the "max_allowed_packet" value is somehow compiled into the module? Should I recompile everything instead of using binary debian packages? Wojtek
