headers
apv | 5 Jan 2006 01:09
Favicon
Gravatar

utf8 support/patch for a dev release?

I found the utf8 support patch for DBD::mysql in the list archives:

http://marc.theaimsgroup.com/?l=msql-mysql-modules&m=111970179409036&w=2

Is there any chance of getting it applied to a dev release and put
up on the CPAN (as a dev release it shouldn't interfere with anyone
but those who want to experiment with it)? I'd love to start working
with it for my current project.

Thank you!
-Ashley

--

-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules <at> m.gmane.org
Permalink | Reply | 1 comment |
headers
Daniel Kasak | 5 Jan 2006 02:01
Picon

Re: utf8 support/patch for a dev release?

apv wrote:

> I found the utf8 support patch for DBD::mysql in the list archives:
>     
> http://marc.theaimsgroup.com/?l=msql-mysql-modules&m=111970179409036&w=2
>
> Is there any chance of getting it applied to a dev release and put
> up on the CPAN (as a dev release it shouldn't interfere with anyone
> but those who want to experiment with it)? I'd love to start working
> with it for my current project.
>
> Thank you!
> -Ashley
>
>
I second that request, and also look forward to testing utf8 support.

-- 
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak <at> nusconsulting.com.au
website: http://www.nusconsulting.com.au

--

-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Kasak | 5 Jan 2006 02:12
Picon

$sth->{'NAME'} and $dbh->column_info() broken in DBD-mysql-3.x ?

Greetings.

Further to unresolved issues I'm having with $dbh->column_info ( see 
post of 2005-10-24 ), I've just discovered that $sth->{'NAME'} is also 
not returning a full field list - I get a truncated list of fields, with 
no errors.

I discovered this when building a new box, and accidentally installed 
DBD-mysql-3.0002_p4. On all our clients now, I have to have < 
DBD-mysql-3.0 or our apps fail when retrieving a field list or column info.

Is anyone else able to reproduce these issues? I've reproduced it on a 
number of different systems. The current one is:

Perl 5.8.7
DBD-mysql-3.0002_p4 compiled against mysql-5.0.18 with gcc-4.0.2
Server running mysql-4.1.14

Previously I've tried systems such as:

Perl 5.8.7
DBD-mysql-3.0002_p3 compied against mysql-5.0.something with gcc-3.4.4
Server running mysql-4.1.14

A simple command such as:

my $sth = "select * from any_table where 0=1";
$sth->execute;
my $fieldlist = $sth->{'NAME'};
(Continue reading)

Permalink | Reply | 1 comment |
headers
Daniel Kasak | 5 Jan 2006 02:15
Picon

Re: $sth->{'NAME'} and $dbh->column_info() broken in DBD-mysql-3.x ?

Daniel Kasak wrote:

>
> my $sth = "select * from any_table where 0=1";

Yeah. Make that:
my $sth = $dbh->prepare("select * from any_table where 0=1");

O:-)

-- 
Daniel Kasak
IT Developer
NUS Consulting Group
Level 5, 77 Pacific Highway
North Sydney, NSW, Australia 2060
T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989
email: dkasak <at> nusconsulting.com.au
website: http://www.nusconsulting.com.au

--

-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules <at> m.gmane.org
Permalink | Reply | 0 comments |
headers
John Chambers | 6 Jan 2006 15:38

warning message: DBI->connect using 'old-style' syntax is depreca ted and will be an error in future versions at blib/lib/invlib.pm line 20

A few weeks ago, I upgraded an old Debian system to Sarge, and I started
receiving these error messages:
DBI->connect using 'old-style' syntax is deprecated and will be an error in
future versions at blib/lib/invlib.pm line 20
in my apache logs.

Now, I'm building a newer system from scratch, and when I make test my local
modules, I'm getting that message.

The scripts still work, but I prefer no warnings

What is the new syntax?  Here is my call:
(my $dbh = DBI->connect( 'sheet', 'jc', 'secret', 'mysql' ) ) or  die
"Cannot do \$dbh->connect: $DBI::errstr\n";

Thanks,
John Chambers

--

-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/perl?unsub=gcdmp-msql-mysql-modules <at> m.gmane.org
Permalink | Reply | 0 comments |
headers
Selke, Gisbert W. | 6 Jan 2006 15:51
Picon

AW: <<Spam-Verdacht>> warning message: DBI->connect using 'old-style' syntax is deprecated and will be an error in future versions at blib/lib/invlib.pm line 20

> -----Ursprüngliche Nachricht-----
> Von: John Chambers [mailto:JLChambers <at> klikwood.com]
> Gesendet: Freitag, 6. Januar 2006 15:39
> A few weeks ago, I upgraded an old Debian system to Sarge, and I started
> receiving these error messages:
> DBI->connect using 'old-style' syntax is deprecated and will 
> be an error in future versions at blib/lib/invlib.pm line 20
> in my apache logs. 
> Now, I'm building a newer system from scratch, and when I 
> make test my local modules, I'm getting that message.
> The scripts still work, but I prefer no warnings
Good idea.

> What is the new syntax?  Here is my call:
> (my $dbh = DBI->connect( 'sheet', 'jc', 'secret', 'mysql' ) ) or  die
> "Cannot do \$dbh->connect: $DBI::errstr\n";
A very brief look into the DBI docs reveals:

  $dbh = DBI->connect($data_source, $username, $password)
            or die $DBI::errstr;
  $dbh = DBI->connect($data_source, $username, $password, \%attr)
            or die $DBI::errstr;
[...]
Examples of $data_source values are:

  dbi:DriverName:database_name
  dbi:DriverName:database_name <at> hostname:port
  dbi:DriverName:database=database_name;host=hostname;port=port
[...]
    For compatibility with old DBI scripts, the driver can be specified by
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Smol | 12 Jan 2006 17:30
Picon

HPUX 11.11 mysql zlib DBD::mysql compile error

Hi great Perl/MySQL Gurus.

I am trying to install and run Mysql on HPUX 11.11 with perl + Mysql
support.
I've downloaded depot distributions of MySQL from mysql website,
installed and it is running fine. 

When I install DBD::mysql I got some error about complaining if
libmysqlclient was compiled with Zlib support.

root <at> czhs0681# perl Makefile.PL --cflags="-I/usr/local/mysql/include -O"
I will use the following settings for compiling and testing:

  cflags        (User's choice) = -I/usr/local/mysql/include -O
  embedded      (mysql_config ) =
  libs          (mysql_config ) = -L/usr/local/mysql/lib -lmysqlclient
-lz -lcrypt -lnsl -lm
  mysql_config  (guessed      ) = mysql_config
  nocatchstderr (default      ) = 0
  nofoundrows   (default      ) = 0
  ssl           (guessed      ) = 0
  testdb        (default      ) = test
  testhost      (default      ) =
  testpassword  (default      ) =
  testsocket    (default      ) =
  testuser      (default      ) =

To change these settings, see 'perl Makefile.PL --help' and
'perldoc INSTALL'.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Beau E. Cox | 16 Jan 2006 01:15
Picon

Blobs broken in DBD-mysql-3.0002_4?

Hi -

Access to blobs seems to be broken in DBD-mysql-3.0002_4
( works fine in DBD-mysql-3.0002 ). I am using perl-5.8.7 and
DBI-1.50 on Gentoo Linux.

Here are the results of my small script ( posted below )
using DBD-mysql-3.0002_4:

$ perl testblob.pl
'blob_test' table created.
blob inserted.
blob select executed.
Out of memory!
Out of memory!
Callback called exit.

Seems to blow up on the fetch.

'testblob.pl' test script:

#-----start------
use strict;
use warnings;
use DBI;

my $database = 'test';         # <- set to your value
my $user = 'whatever';         # <- set to your value
my $password = 'whatever';     # <- set to your value
(Continue reading)

Permalink | Reply | 0 comments |
headers
Douglas S. Davis | 16 Jan 2006 17:24
Favicon

Query Question

Hi,

If the following isn't appropriate, please feel free to ignore.  The 
program I'm referring to is written in Perl and uses a MySQL 
database, so I thought perhaps it would be appropriate for this list.

I have a webpage that displays a user's profile by selecting the data 
in the "profiles" database that corresponds to the user's ID number 
(in the profiles database that number is stored as the "id_num"). I 
have another table that stores comments that are posted to each 
user's profile page.

What I need to do is:

#1)  Display a user's profile by looking up the data in the profiles database.

#2)  Look in the comments database for any comments that have the 
user's id_num associated with it, and display the comments and the 
comment posters' names as found by querying the profile database on 
the comment posters' ID numbers.

Can this be accomplished with a join.

Basically two tables with data similar to this:

Profiles Table
----------------------------
| id |      name      |
________________
| 1 | Bill Clinton    |
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Stassen | 16 Jan 2006 17:42
Picon

Re: Query Question

Douglas S. Davis wrote:
> Hi,
> 
> If the following isn't appropriate, please feel free to ignore.  The 
> program I'm referring to is written in Perl and uses a MySQL database, 
> so I thought perhaps it would be appropriate for this list.
> 
> I have a webpage that displays a user's profile by selecting the data in 
> the "profiles" database that corresponds to the user's ID number (in the 
> profiles database that number is stored as the "id_num"). I have another 
> table that stores comments that are posted to each user's profile page.
> 
> What I need to do is:
> 
> #1)  Display a user's profile by looking up the data in the profiles 
> database.
> 
> #2)  Look in the comments database for any comments that have the user's 
> id_num associated with it, and display the comments and the comment 
> posters' names as found by querying the profile database on the comment 
> posters' ID numbers.
> 
> Can this be accomplished with a join.
> 
> Basically two tables with data similar to this:
> 
> Profiles Table
> ----------------------------
> | id |      name      |
> ________________
(Continue reading)

Permalink | Reply | 0 comments |

Gmane