gmane.comp.db.mysql.perl

Query

Mia Smith — 2013-06-18T07:00:19

Hi,

My name is Mia Smith and I manage the website Lacartes.com. We are expa
nding our online marketplace in your area and I was wondering if you'd like 
to add your business to our website for free? Our website is helping 400,000
+ people every month find the businesses, products and services they need. W
e'd like to invite you to create a free business page on our website so our 
users will be able to find you and share your offerings with their friends a
nd families.

Your business page lets you publish photos, prices, videos, ne
ws announcements and communicate directly with customers. It will appear on 
all major search engines like Google so you will benefit from instant online
 exposure to a large audience looking for the products and services you offe
r. It will also feature a permanent link to send visitors to your own websit
e. We make money through thirdparty ad banners so we do not charge businesse
s anything to use our website. Our goal is to grow our user base and help mo
re people connect with

Re: Please update DBD::MySQL with how to create test database

Phil Dobbin — 2013-04-13T19:04:51


Aren't the details in perlpod? That's what cpanm tells me every time I
install it.

Cheers,

  Phil...

Please update DBD::MySQL with how to create test database

David Favor — 2013-04-13T16:20:17

make test fails for me, regardless of how I've created
the test database.

To simplify everyone's life.

Please add the exact command line commands for creating
the test database, so make test passes all tests.

Specifically this includes creating the test user with
an empty password, which seems to be the failure point.

Thanks.

Re: Still active?

Darren Duncan — 2013-04-12T05:28:58

This list is still around, but almost no activity.  I've been on it for several 
years, and count 6 messages to it in 2012, 5 in February and 1 in July. -- 
Darren Duncan

Still active?

Lyle — 2013-04-12T00:30:08

Hi,
   Is this list still active? I've found that DBD::mysql bugs are no 
longer reported via the mysql bug tracker:
http://bugs.mysql.com/bug.php?id=68266
Is this list going as well?


Lyle

question about stored procedures with Select statements and critical errors.

Kern, Daniel — 2012-07-19T12:34:46

Can someone please help with the following.  I am using mysql dbd 4.017 and mysql 5.5.17.

When I call a stored procedure that has Select statements in it, and the stored procedure has a critical error, I am not getting back any indication there was an error.

The SP looks like this:
Begin
SELECT CONCAT("Populating summary tables from: ",< at >v_from_date, " , to: ",< at >v_to_date) AS return_message;
...
<Critical Error here>
...
End

Here is the code, where $sql is call <sp name> (\'2012-06-16\', \'2012-06-16\')
              $sth = $dbh->prepare($sql);
              if (!$sth) {
...
              }
             my $ex_result = $sth->execute();


And when I run in the debugger, I get this result on the statement handle:
x DBI::dump_results($sth):
'Populating summary tables from...'
1 rows

0         1

And x $sth->errstr returns:
undef

RaiseError is off.  If I set it to On, I then need to run the execute in an eval statement.  But this is not necessary if there is no Select statement in the SP - in that case I get

Re: AW: bind parameter guessing corrupts results

Marc Lehmann — 2012-02-29T10:28:12

Well, the solution I outlined has the advantage of being dwim but at
the same time doesn't suffer from arbitraryness - that is, there is a
consistent way of marking numbers as numbers, even with perl.

So your argument is wrong - the problem is not dwim here.

The problem is the arbitraryness - even if perl thinks something is a
number and doesn't even have alternatives, dbd::mysql would still quote it
if it becomes too big, and this behaviour isn't even clearly documented.

AW: bind parameter guessing corrupts results

Selke, Gisbert W. — 2012-02-28T21:20:34

Same, btw, for Gisle Aas's data::Dump -- it quotes some numbers but not others (unless you use quote(), in which case it consistently quotes all numbers).
That's the price you pay for dwimmyness: sometimes it bites you. Especially when you least expect it.

\Gisbert

Re: bind parameter guessing corrupts results

Marc Lehmann — 2012-02-23T03:27:48

First, thanks for replying, although the way you format your e-mail makes
me dizzy reading it - couldn't you set your mua to a fixed line width
instead of alternating long and short lines?


No, the rules are much more complicated:
http://dev.mysql.com/doc/refman/5.0/en/type-conversion.html


No, the only column types for which there are magical behaviours are
TIMESTAMP and DATETIME. And this also doesn't work for IN. In reality
mysql uses the types of both operands instead.


The column in question is:

| mtime | int(10) unsigned                                   | NO   | MUL | 0

and the key is not used for e.g. '1329967147' when quoted, which mysql
does.  It doesn't quote all numbers, which is why this problem went
undetected until the numbers became "large".


Well, in many versions of DBD::mysql this behaviour is the default (also
documented).

What is dnagerous is the constant changing of the heuristic - the current
code quotes _some_ numbers (if they are "big") but not others for example.


Or, alter

RE: bind parameter guessing corrupts results

Neubauer, Ralf — 2012-02-22T16:05:46

Hi!



I just tried it (with 5.5.10 and 5.1.44):

select t.*,
  i < 15, s < 15, i < '15', s < '15'
from (
  select i, concat(i) s
  from (
    select 1 i union select 2 union select 3 union select 4 union select
5 union select 6
    union select 7 union select 8 union select 9 union select 10 union
select 11
    union select 12 union select 13 union select 14 union select 15
union select 16
    union select 17 union select 18 union select 19 union select 20
  ) t
) t
order by i

As you can see, everything is ok. Quoted numbers are converted to
numbers by MySQL, if
the column they are compared with is numeric. On the other hand, if the
column is a
string and the constant is a number, the column is forced to be a number
(which can be a
real problem, if there are non-numeric values in the column). Only if
you compare a
string column with a string constant, both are compared as strings.

I assume that is what you do in your program, you store numbers in a
string column and
want them to be compared as a number. I

bind parameter guessing corrupts results

Marc Lehmann — 2012-02-13T03:01:35

Hi!

We today upgraded DBD::mysql to 4.020, and some of our scripts started to
work very slowly.

The reason was quickly found to be an integer that was stringified in the
current version of DBD::mysql.

In old versions of DBD::mysql, one could get reliable behaviour by using e.g.

   $num*1   # for numbers
   "string" # for strings

it seems in current versions of DBD::mysql there is some autoguessing
going on, which seems to be wrong in many cases, and doesn't seem to be
documented at all.

Worse, whoeveer wrote the documentation seems to think this is a
performance issue in mysql only, however, this is a correctness issue, and
in our case, this even corrupts the results.

For example, in (my-)sql, the following statements do not have the same
semantics:

   col < 10
   col < "10"

For col = 5, the first is true, the second is false, and an update statement
using newer DBD::mysql would update the wrong rows, apart from potentially
being slower.

Looking at the changes, the type of guessing applied seems to

DBD::drizzle version 0.304 released

Patrick Galbraith — 2011-11-03T22:04:35

Hi!

I have released DBD::drizzle version 0.304 as today. This release
includes much easier building than before. The Makefile.PL now does a
much better job of finding the libdrizzle headers and libraries.

For this release, please go to:
http://search.cpan.org/~capttofu/DBD-drizzle-0.304/lib/DBD/drizzle.pm.

You can also obtain the latest source from Launchpad: bzr branch lp:dbd-drizzle

Thank you for using DBD::drizzle and Drizzle itself, and have fun!

regards,

Patrick "CaptTofu" Galbraith

DBD::mysql: no errstr under Windows

Neubauer, Ralf — 2011-10-18T16:13:29

Hi,

as you may have seen in https://rt.cpan.org/Public/Bug/Display.html?id=71047 or even in http://bugs.activestate.com/show_bug.cgi?id=91026 there is no ->errstr or ->err on the Windows platform, if ->execute failed.

In DBD::mysql 4.018 the code at the end of mysql_st_internal_execute() in dbdimp.c that executed the statement and transferred the error codes looked like this:

if ((mysql_real_query(svsock, sbuf, slen))  &&
      (!mysql_db_reconnect(h)  ||
       (mysql_real_query(svsock, sbuf, slen))))
  {
    Safefree(salloc);
    do_error(h, mysql_errno(svsock), mysql_error(svsock), 
             mysql_sqlstate(svsock));
    if (DBIc_TRACE_LEVEL(imp_xxh) >= 2)
      PerlIO_printf(DBILOGFP, "IGNORING ERROR errno %d\n", errno);
    return -2;
  }
  Safefree(salloc);

In 4.020 it looks like this (Note that MYSQL_ASYNC is 0 on the Windows platform as defined in dbdimp.h):

#if MYSQL_ASYNC
  if(async) {
    if((mysql_send_query(svsock, sbuf, slen)) &&
       (!mysql_db_reconnect(h) ||
        (mysql_send_que

want to install mysql client only

Hauck, John P [ITSYS] — 2011-09-29T21:35:13

I am trying to do a client-only install of mysql on a Solaris 10 zone so I can access a mysql db on a remote machine using DBD::mysql.  Can someone please point me at some instructions for doing this?  I'm trying to do this with mysql 5.0.67 using "-without-server" on ./configure.  I'm getting

   "make: Fatal error:  Command failed for target `all-recursive' "

from the make.

The environment is:

Solaris 10 10/08 s10s_u6wos_07b SPARC

host> gcc -v
Reading specs from /usr/local/lib/gcc/sparc-sun-solaris2.10/3.4.6/specs
Configured with: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --enable-shared --enable-languages=c,c++,f77
Thread model: posix
gcc version 3.4.6

configure:
CC=gcc
CCFLAGS=-Xa -fast -native -xstrconst -mt -m64
CXX=CC
CXXFLAGS=-noex -mt -m64

./configure --prefix=/usr/local/mysql --without-server --with-extra-charsets=complex --enable-thread-safe-client --enable-local-infile --with-named-z-libs=no --with-named-curses-libs=-lcurses --enable-shared --with-zlib-dir=bundled --w

nature of the server side prepared statement issues?

Corey Hickey — 2011-09-26T01:10:39

Hi,

I see in the documentation:
-----------------------------------------------------------------------
As of 3.0002_1, server side prepare statements were on by default (if
your server was >= 4.1.3). As of 3.0009, they were off by default again
due to issues with the prepared statement API (all other mysql
connectors are set this way until C API issues are resolved). The
requirement to use prepared statements still remains that you have a
server >= 4.1.3
-----------------------------------------------------------------------

Can somebody please tell me what the API issues are/were or point me to
something more specific I can read? I am having trouble finding out for
myself whether these issues are pertinent to me.

Thanks,
Corey

can't call statistics_info() method

Keedi Kim — 2011-08-30T03:26:35

Hi,

I have a problem to call statistics_info() method since 4.019.
I'm using DBD::mysql with Fey::Loader and before DBD::mysql 4.019,
Fey::Loader::mysql module has a fix up code to call statistics_info method.


Since DBD::mysql 4.019, following code was added.

quote_identifier begin_work/;

But when $dbh->statistics_info() method is called,
following error message is occurred.

Can't locate object method "statistics_info" via package
"DBD::mysql::db::SUPER" at
/home/askdna/perl5/perlbrew/perls/perl-5.14.1/lib/site_perl/5.14.1/i686-linux/DBD/
mysql.pm line 767.

my little script which call stastics_info() method looks like:


Could you please tell me what is wrong in my code
or what I mis-understand about DBD::mysql.

Thanks :-)

Best Regards,

Keedi Kim

----
http://keedi.pe.kr

DBD::mysql 4.020 released

Patrick Galbraith — 2011-08-24T13:20:31

Dear Perl community,

I'm pleased to announce the release of DBD::mysql, the MySQL Perl
client, 4.020. The release has several great fixes provided by the
community, and in particular from Masahiro Chiba, who fixed several
issues pertaining to prepared statement support as well as UTF8
support, something that I myself have had a difficult time fixing and
testing.

From the Change log:

2011-08-15 Patrick Galbraith <patg at patg dot net> (4.020)
* Numerous (!! Thank you!!) fixes for prepared statements: Masahiro
Chiba <nihen at megabbs
dot com>
- Chop blanks fixed
- UTF8 improvements
- fixed memory allocation for BLOBs
- auto-reconnect
* Fix in leak test, which failed sometime due to first assignment
$prev_size over
paging (Masahiro Chiba)
* Catalog test allows use of schemas other than 'test' (Masahiro Chiba)
* Documentation fix for auto_reconnect (Karen Etheridge <ether at cpan dot
org>)
* Win32 and general installation fixes (Alexandr Ciornii, http://chorny.net)

I want to thank Masahiro, Karen and Ale

How to install DBD::mysql at Macosx

Takaaki T. Komatsu — 2011-06-11T02:39:46

Dear Sirs,

I'm try to install mysql and perl at my computer.
with in the CPAN installation I got a error msg.
would you please tell me ha to fix....
Best regards,

Takaaki Komatsu

H/W: MacBookPro
S/W: Mac OSX 10.6.7
Perl:5.14.0
mysql:5.5.13.0 osx

cpan[1]> install DBD::mysql
Going to read '/Users/tti/.cpan/Metadata'
  Database was generated on Fri, 10 Jun 2011 05:29:39 GMT
Running install for module 'DBD::mysql'
Running make for C/CA/CAPTTOFU/DBD-mysql-4.019.tar.gz
Checksum for /Users/tti/.cpan/sources/authors/id/C/CA/CAPTTOFU/DBD-mysql-4.019.tar.gz ok
Scanning cache /Users/tti/.cpan/build for sizes
............................................................................DONE

  CPAN.pm: Going to build C/CA/CAPTTOFU/DBD-mysql-4.019.tar.gz



PLEASE NOTE:

For 'make test' to run properly, you must ensure that the 
database user 'tti' can connect to your MySQL server 
and has the proper privileges that these tests require such 
as 'drop table', 'create table', 'drop procedure', 'create procedure'
as well

Re: DBD::mysql 4.019 Released

Curtis Jewell — 2011-05-11T05:10:28

On Mon, 09 May 2011 14:24 -0400, "Patrick Galbraith" <patg< at >patg.net>
wrote:

And I'm sorry to say that it DOES NOT COMPILE on Strawberry Perl 5.10.x
32-bit or 5.12.x 64-bit:

Putting it in the compilation chain:
http://hg.curtisjewell.name/Perl-Dist-Strawberry/rev/5659321f22fa

Taking it back out:
http://hg.curtisjewell.name/Perl-Dist-Strawberry/rev/6eabb352a96d

Why? (64-bit output, 32-bit is similar)

STDOUT:
cp lib/DBD/mysql.pm blib\lib\DBD\mysql.pm
cp lib/DBD/mysql/GetInfo.pm blib\lib\DBD\mysql\GetInfo.pm
cp lib/DBD/mysql/INSTALL.pod blib\lib\DBD\mysql\INSTALL.pod
cp lib/Bundle/DBD/mysql.pm blib\lib\Bundle\DBD\mysql.pm
gcc -c  -IC:\strawberry\perl\vendor\lib\auto\DBI
-IC:\strawberry\c\bin\..\include\mysql_5 -DDBD_MYSQL_INSERT_ID_IS_GOOD
-g      -s -O2 -DWIN32 -DHAVE_DES_FCRYPT -DWIN64 -DCONSERVATIVE
-DUSE_SITECUSTOMIZE -DPERL_IMPLICIT_CONTEXT -DPERL_IMPLICIT_SYS
-fno-strict-aliasing -mms-bitfields -DPERL_MSVCRT_READFIX -s -O2        
 -DVERSION=\"4.019\"   -DXS_VERSION=\"4.019\" 
"-IC:\strawberry\perl\li

Re: DBD::mysql 4.019 Released

Tim Bunce — 2011-05-09T19:08:54

That's great, but...


... that should be 'mysql_async'. I.e., the name of the driver-private
attribute should include the drivers prefix.

Please add mysql_async and deprecate async in the next release.

Tim.

DBD::mysql 4.019 Released

Patrick Galbraith — 2011-05-09T18:24:21

Dear Perl and MySQL enthusiasts,

I’m pleased to announce the release of DBD::mysql 4.019. I’m
especially pleased because there are some new enhancements and
features that have been provided by contributions from the community:

* Asynchronous support, added by Rob Hoelz. This is a new feature to
DBD::mysql that takes advantage of libmysql’s asynchronous functions
(see Jan’s article from 2008
http://jan.kneschke.de/2008/9/9/async-mysql-queries-with-c-api/) .
From the DBD::mysql documentation:

You can make a single asynchronous query per MySQL connection; this
allows you to submit a long-running query to the server and have an
event loop
inform you when it’s ready. An asynchronous query is started by either
setting the ‘async’ attribute to a true value in the DBI do() method,
or in the DBI prepare() method. Statements created with async set to
true in prepare always run their queries asynchronously when DBI
execute() is called. The driver also offers three additional methods:
mysql_async_result