sqlgrey-users

[Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juraj V. <ju...@eq...>]

Hello,

I am trying to set it up on Debian Sarge.  In /etc/sqlgrey/sqlgrey.conf I have 
only:

db_type=mysql
db_name=sqlgrey
db_user=XXXX
db_pass=YYYY

When I start sqlgrey, it dies and leaves following in syslog. The db_user and 
pass are correct. Please advise where could be the problem.

Jan 10 16:07:28 testserver sqlgrey: Process Backgrounded
Jan 10 16:07:28 testserver sqlgrey: 2007/01/10-16:07:28 sqlgrey (type 
Net::Server::Multiplex) starting! pid(1658)
Jan 10 16:07:28 testserver sqlgrey: Binding to TCP port 2501 on host localhost
Jan 10 16:07:28 testserver sqlgrey: Setting gid to "109 109"
Jan 10 16:07:28 testserver sqlgrey: Setting uid to "108"
Jan 10 16:07:28 testserver sqlgrey: warning: Use of uninitialized value in 
concatenation (.) or string at /usr/local/sbin/sqlgrey line 227.
Jan 10 16:07:28 testserver sqlgrey: dbaccess: warning: couldn't do query: 
CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, sender_domain 
varchar(255) NOT NULL, src va
rchar(39) NOT NULL, first_seen timestamp NOT NULL, last_seen timestamp NOT 
NULL, PRIMARY KEY (src, sender_domain, sender_name)): , reconnecting to DB
Jan 10 16:07:28 testserver sqlgrey: mail: child exited with value: 1
Jan 10 16:07:28 testserver sqlgrey: fatal: create_from_awl_table error 
at /usr/local/sbin/sqlgrey line 176.


-- 
Juraj Variny <ju...@eq...>

Administrator, Developer
Equilibrium Ltd. / Rovnovaha s r.o.
http://www.equit.sk/

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Dan F. <da...@ha...>]

Not sure. I run on several sqlgreys on Debian Sarge myself and havnt had 
this problem.

But i do seem to recall that the default Debian settings for Mysql is 
either having "skip-networking" enabled or bind to 127.0.0.1 (depending 
on versions).

If skip-networking is enabled, that would definently explain it, as 
sqlgrey doesn't connect through the socket file 
"/var/run/mysqld/mysqld.sock" like eg. php does pr. default.

and if mysql is bound to 127.0.0.1 and youre using the servers real ip 
or hostname in db_host, then that would also explain your problem.

- Dan



Juraj Variny wrote:
> Hello,
>
> I am trying to set it up on Debian Sarge.  In /etc/sqlgrey/sqlgrey.conf I have 
> only:
>
> db_type=mysql
> db_name=sqlgrey
> db_user=XXXX
> db_pass=YYYY
>
> When I start sqlgrey, it dies and leaves following in syslog. The db_user and 
> pass are correct. Please advise where could be the problem.
>
> Jan 10 16:07:28 testserver sqlgrey: Process Backgrounded
> Jan 10 16:07:28 testserver sqlgrey: 2007/01/10-16:07:28 sqlgrey (type 
> Net::Server::Multiplex) starting! pid(1658)
> Jan 10 16:07:28 testserver sqlgrey: Binding to TCP port 2501 on host localhost
> Jan 10 16:07:28 testserver sqlgrey: Setting gid to "109 109"
> Jan 10 16:07:28 testserver sqlgrey: Setting uid to "108"
> Jan 10 16:07:28 testserver sqlgrey: warning: Use of uninitialized value in 
> concatenation (.) or string at /usr/local/sbin/sqlgrey line 227.
> Jan 10 16:07:28 testserver sqlgrey: dbaccess: warning: couldn't do query: 
> CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, sender_domain 
> varchar(255) NOT NULL, src va
> rchar(39) NOT NULL, first_seen timestamp NOT NULL, last_seen timestamp NOT 
> NULL, PRIMARY KEY (src, sender_domain, sender_name)): , reconnecting to DB
> Jan 10 16:07:28 testserver sqlgrey: mail: child exited with value: 1
> Jan 10 16:07:28 testserver sqlgrey: fatal: create_from_awl_table error 
> at /usr/local/sbin/sqlgrey line 176.
>
>
>   

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Winfried N. <win...@ne...>]

Hi,

* Dan Faerch <da...@ha...>:

> If skip-networking is enabled, that would definently explain it, as
> sqlgrey doesn't connect through the socket file=20
> "/var/run/mysqld/mysqld.sock" like eg. php does pr. default.
>
That's not true. sqlgrey uses Perl's DBI mechanism, which is working
fine with connecting via socket. In fact it's working exactly the same
way here for me (Debian Sarge with self-compiles MySQL)

MySQL is started with UNIX socket only:
,---[ grep networking /etc/my.cnf ]
| skip-networking
`----

No my MySQL is listening on TCP port 3306:
,---[ lsof -n -i :3306 ]
|
`----

As sqlgrey doesn't seem to return the error why the query failed,
,---
| [...]
| Use of uninitialized value in concatenation (.) or string at
| /usr/local/sbin/sqlgrey line 227.
|
| (which would be the $DBI::errstr here
`---
please open a shell an execute this line an send us what error that is
returned by it:

,---
| perl -MDBI -le 'my $db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=
=3Dlocalhost","youruser","yourpass",undef) or die "Error: $DBI::errstr"$db-=
>disconnect()'
`---

Regards
Winfried

--=20
Winfried Neessen                           Phone:       +49 221 2612601
neessen.net - Webhosting                   Fax:         +49 221 2612602
Peter-Bauer-Str. 9                         Email:  win...@ne...
50823 Cologne                              PGP/GPG Key-ID:   0xda5cd8ef

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juraj V. <ju...@eq...>]

Hello,

I am sending following message again, sorry if you already got it. It did 
arrive back to me, but in web archive of this mailinglist isn't visible.

---------

 perl -MDBI -le 'my 
$db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","myuser","mypass",undef) 
or die "Error:$DBI::errstr".$db->disconnect()'

 passed without failure and output nothing. Then I tried to create the table, 
with very interesting result:

perl -MDBI -le 'my 
$db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","u_sqlgrey","greysql",undef); 
$db->do("CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, 
sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, first_seen 
timestamp NOT NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src, 
sender_domain, sender_name))");$db->disconnect();'
DBD::mysql::db do failed: Specified key was too long; max key length is 1000 
bytes at -e line 1.

According to http://bugs.mysql.com/bug.php?id=4541 , it seems the culprit is 
that I have utf8 database....

Juraj

On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
(snip)
> `---
> please open a shell an execute this line an send us what error that is
> returned by it:
>
> ,---
>
> | perl -MDBI -le 'my
> | $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","youruser","
> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
>
> `---
>
> Regards
> Winfried

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Dan F. <da...@ha...>]

Winfried Neessen wrote:
> That's not true. sqlgrey uses Perl's DBI mechanism, which is working
> fine with connecting via socket. In fact it's working exactly the same
>
>   
Really? Then i stand corrected..But havent you then explicitly defined 
the socket file and not an IP? or at least 127.0.0.1 as the IP?

- Dan

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Winfried N. <win...@ne...>]

Hi Dan,

* Dan Faerch <da...@ha...>:

>> That's not true. sqlgrey uses Perl's DBI mechanism, which is working
>> fine with connecting via socket. In fact it's working exactly the same
>>
> Really? Then i stand corrected..But havent you then explicitly defined
> the socket file and not an IP? or at least 127.0.0.1 as the IP?
>
Nop ;-) I defined these db specific parameters:
,---[ /etc/sqlgrey/sqlgrey.conf ]
| db_type =3D mysql
| db_name =3D sqlgrey
| db_host =3D localhost
| db_user =3D xxxxx
| db_pass =3D yyyyy
`---

But if I wouldn't have defined db_host in /etc/sqlgrey/sqlgrey.conf
it would use localhost by default as defined in sqlgres:
,---
| $dflt{db_host}            =3D 'localhost';
`---

Winfried

--=20
Winfried Neessen                           Phone:       +49 221 2612601
neessen.net - Webhosting                   Fax:         +49 221 2612602
Peter-Bauer-Str. 9                         Email:  win...@ne...
50823 Cologne                              PGP/GPG Key-ID:   0xda5cd8ef

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juraj V. <ju...@eq...>]

Hello,

 perl -MDBI -le 'my $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","myuser","mypass",undef) or die "Error:$DBI::errstr".$db->disconnect()'

 passed without failure and output nothing. Then I tried to create the table, with very interesting result:

perl -MDBI -le 'my $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","u_sqlgrey","greysql",undef); $db->do("CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src, sender_domain, sender_name))");$db->disconnect();'
DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at -e line 1.

According to http://bugs.mysql.com/bug.php?id=4541 , it seems the culprit is that I have utf8 database....

Juraj

On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
(snip)
> `---
> please open a shell an execute this line an send us what error that is
> returned by it:
>
> ,---
>
> | perl -MDBI -le 'my
> | $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","youruser","
> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
>
> `---
>
> Regards
> Winfried

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Dan F. <da...@ha...>]

Ahh yes...

Lionel helped someone not long ago who had problems, and it turned out 
to be a UNICODE problem. Here's a quote from the mailing list:

"Hum, did you try to use a database with ASCII instead of UNICODE?
SQLgrey doesn't try to speak utf-8 with the database but only pure ASCII."

Andrew wrote a helpfull mail on how to migrate to ASCII.
 From the maillinglist archives:
http://sourceforge.net/mailarchive/message.php?msg_id=37802061


On a side note. Since more ppl will have this problem, im thinking we 
should either support other encodings or at least warn on execution of 
sqlgrey.

Anyone got some thoughts about either of theese?
- How hard is it to support all encodings
- How do we detect if database is ASCII

If we get a real simple solution, ill try and implement it very soon.

- Dan


Juraj Variny wrote:
> Hello,
>
>  perl -MDBI -le 'my $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","myuser","mypass",undef) or die "Error:$DBI::errstr".$db->disconnect()'
>
>  passed without failure and output nothing. Then I tried to create the table, with very interesting result:
>
> perl -MDBI -le 'my $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","u_sqlgrey","greysql",undef); $db->do("CREATE TABLE from_awl (sender_name varchar(64) NOT NULL, sender_domain varchar(255) NOT NULL, src varchar(39) NOT NULL, first_seen timestamp NOT NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src, sender_domain, sender_name))");$db->disconnect();'
> DBD::mysql::db do failed: Specified key was too long; max key length is 1000 bytes at -e line 1.
>
> According to http://bugs.mysql.com/bug.php?id=4541 , it seems the culprit is that I have utf8 database....
>
> Juraj
>
> On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
> (snip)
>   
>> `---
>> please open a shell an execute this line an send us what error that is
>> returned by it:
>>
>> ,---
>>
>> | perl -MDBI -le 'my
>> | $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","youruser","
>> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
>>
>> `---
>>
>> Regards
>> Winfried
>>     
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>   

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juan P. B. <jp...@gr...>]

Im really a newbbie with MySql and i get LOADS of these:

SQLgrey recovered DB:	SQLgrey established connection to:
DBI:mysql:database=3DSqlgrey;host=3Dlocalhost
SQLgrey database error:	SQLgrey encountered an SQL error and triggered a
reconnection to: DBI:mysql:database=3DSqlgrey;host=3Dlocalhost

Cluopd it be the same problem?
How can i do it with mysql?
I got this:

character set latin1=20

character sets latin1 big5 czech euc_kr gb2312 gbk=20
latin1_de sjis tis620 ujis dec8 dos german1 hp8 koi8_ru=20
latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian=20
koi8_ukr win1251ukr greek win1250 croat cp1257 latin5=20


> -----Original Message-----
> From: sql...@li...=20
> [mailto:sql...@li...] On=20
> Behalf Of Dan Faerch
> Sent: Thursday, January 11, 2007 17:03
> To: SQLgrey users mailing-list
> Subject: Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables
>=20
>=20
> Ahh yes...
>=20
> Lionel helped someone not long ago who had problems, and it=20
> turned out=20
> to be a UNICODE problem. Here's a quote from the mailing list:
>=20
> "Hum, did you try to use a database with ASCII instead of UNICODE?
> SQLgrey doesn't try to speak utf-8 with the database but only=20
> pure ASCII."
>=20
> Andrew wrote a helpfull mail on how to migrate to ASCII.
>  From the maillinglist archives:
> http://sourceforge.net/mailarchive/message.php?msg_id=3D37802061
>=20
>=20
> On a side note. Since more ppl will have this problem, im thinking we=20
> should either support other encodings or at least warn on=20
> execution of=20
> sqlgrey.
>=20
> Anyone got some thoughts about either of theese?
> - How hard is it to support all encodings
> - How do we detect if database is ASCII
>=20
> If we get a real simple solution, ill try and implement it very soon.
>=20
> - Dan
>=20
>=20
> Juraj Variny wrote:
> > Hello,
> >
> >  perl -MDBI -le 'my=20
> $db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> myuser","mypass",undef) or die "Error:$DBI::errstr".$db->disconnect()'
> >
> >  passed without failure and output nothing. Then I tried to=20
> create the table, with very interesting result:
> >
> > perl -MDBI -le 'my=20
> $db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> u_sqlgrey","greysql",undef); $db->do("CREATE TABLE from_awl=20
> (sender_name varchar(64) NOT NULL, sender_domain varchar(255)=20
> NOT NULL, src varchar(39) NOT NULL, first_seen timestamp NOT=20
> NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src,=20
> sender_domain, sender_name))");$db->disconnect();'
> > DBD::mysql::db do failed: Specified key was too long; max=20
> key length is 1000 bytes at -e line 1.
> >
> > According to http://bugs.mysql.com/bug.php?id=3D4541 , it=20
> seems the culprit is that I have utf8 database....
> >
> > Juraj
> >
> > On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
> > (snip)
> >  =20
> >> `---
> >> please open a shell an execute this line an send us what=20
> error that is
> >> returned by it:
> >>
> >> ,---
> >>
> >> | perl -MDBI -le 'my
> >> |=20
> $db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> youruser","
> >> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
> >>
> >> `---
> >>
> >> Regards
> >> Winfried
> >>    =20
> >
> >=20
> --------------------------------------------------------------
> -----------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the=20
> chance to share your
> > opinions on IT & business topics through brief surveys -=20
> and earn cash
> >=20
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
&CID=3DDEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>  =20


-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Sqlgrey-users mailing list
Sql...@li...
https://lists.sourceforge.net/lists/listinfo/sqlgrey-users

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Gonzalo F. <eat...@gm...>]

what is the MYSQL Version?

some critical changes in the latests version impact in the table
creation an data manipulation.
It looks like the connection is ok, but NOT the table creation. Have you
checked any mysql error in /var/log?

Juan Pablo Bagnon wrote:
> Im really a newbbie with MySql and i get LOADS of these:
>
> SQLgrey recovered DB:	SQLgrey established connection to:
> DBI:mysql:database=Sqlgrey;host=localhost
> SQLgrey database error:	SQLgrey encountered an SQL error and triggered a
> reconnection to: DBI:mysql:database=Sqlgrey;host=localhost
>
> Cluopd it be the same problem?
> How can i do it with mysql?
> I got this:
>
> character set latin1 
>
> character sets latin1 big5 czech euc_kr gb2312 gbk 
> latin1_de sjis tis620 ujis dec8 dos german1 hp8 koi8_ru 
> latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian 
> koi8_ukr win1251ukr greek win1250 croat cp1257 latin5 
>
>
>   
>> -----Original Message-----
>> From: sql...@li... 
>> [mailto:sql...@li...] On 
>> Behalf Of Dan Faerch
>> Sent: Thursday, January 11, 2007 17:03
>> To: SQLgrey users mailing-list
>> Subject: Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables
>>
>>
>> Ahh yes...
>>
>> Lionel helped someone not long ago who had problems, and it 
>> turned out 
>> to be a UNICODE problem. Here's a quote from the mailing list:
>>
>> "Hum, did you try to use a database with ASCII instead of UNICODE?
>> SQLgrey doesn't try to speak utf-8 with the database but only 
>> pure ASCII."
>>
>> Andrew wrote a helpfull mail on how to migrate to ASCII.
>>  From the maillinglist archives:
>> http://sourceforge.net/mailarchive/message.php?msg_id=37802061
>>
>>
>> On a side note. Since more ppl will have this problem, im thinking we 
>> should either support other encodings or at least warn on 
>> execution of 
>> sqlgrey.
>>
>> Anyone got some thoughts about either of theese?
>> - How hard is it to support all encodings
>> - How do we detect if database is ASCII
>>
>> If we get a real simple solution, ill try and implement it very soon.
>>
>> - Dan
>>
>>
>> Juraj Variny wrote:
>>     
>>> Hello,
>>>
>>>  perl -MDBI -le 'my 
>>>       
>> $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","
>> myuser","mypass",undef) or die "Error:$DBI::errstr".$db->disconnect()'
>>     
>>>  passed without failure and output nothing. Then I tried to 
>>>       
>> create the table, with very interesting result:
>>     
>>> perl -MDBI -le 'my 
>>>       
>> $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","
>> u_sqlgrey","greysql",undef); $db->do("CREATE TABLE from_awl 
>> (sender_name varchar(64) NOT NULL, sender_domain varchar(255) 
>> NOT NULL, src varchar(39) NOT NULL, first_seen timestamp NOT 
>> NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src, 
>> sender_domain, sender_name))");$db->disconnect();'
>>     
>>> DBD::mysql::db do failed: Specified key was too long; max 
>>>       
>> key length is 1000 bytes at -e line 1.
>>     
>>> According to http://bugs.mysql.com/bug.php?id=4541 , it 
>>>       
>> seems the culprit is that I have utf8 database....
>>     
>>> Juraj
>>>
>>> On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
>>> (snip)
>>>   
>>>       
>>>> `---
>>>> please open a shell an execute this line an send us what 
>>>>         
>> error that is
>>     
>>>> returned by it:
>>>>
>>>> ,---
>>>>
>>>> | perl -MDBI -le 'my
>>>> | 
>>>>         
>> $db=DBI->connect("DBI:mysql:database=sqlgrey;host=localhost","
>> youruser","
>>     
>>>> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
>>>>
>>>> `---
>>>>
>>>> Regards
>>>> Winfried
>>>>     
>>>>         
>>>       
>> --------------------------------------------------------------
>> -----------
>>     
>>> Take Surveys. Earn Cash. Influence the Future of IT
>>> Join SourceForge.net's Techsay panel and you'll get the 
>>>       
>> chance to share your
>>     
>>> opinions on IT & business topics through brief surveys - 
>>>       
>> and earn cash
>>     
>> http://www.techsay.com/default.php?page=join.php&p=sourceforge
>>     
> &CID=DEVDEV
>   
>> _______________________________________________
>> Sqlgrey-users mailing list
>> Sql...@li...
>> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>>
>>   
>>     
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>   

Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables

[Juan P. B. <jp...@gr...>]

MySql 4.0.24

I have turned log and log-error to try to catch any mysql complaint.


> -----Original Message-----
> From: sql...@li...=20
> [mailto:sql...@li...] On=20
> Behalf Of Gonzalo Fernandez
> Sent: Thursday, January 11, 2007 21:14
> To: SQLgrey users mailing-list
> Subject: Re: [Sqlgrey-users] Sqlgrey dies while creating mysql tables
>=20
>=20
> what is the MYSQL Version?
>=20
> some critical changes in the latests version impact in the table
> creation an data manipulation.
> It looks like the connection is ok, but NOT the table=20
> creation. Have you
> checked any mysql error in /var/log?
>=20
> Juan Pablo Bagnon wrote:
> > Im really a newbbie with MySql and i get LOADS of these:
> >
> > SQLgrey recovered DB:	SQLgrey established connection to:
> > DBI:mysql:database=3DSqlgrey;host=3Dlocalhost
> > SQLgrey database error:	SQLgrey encountered an SQL=20
> error and triggered a
> > reconnection to: DBI:mysql:database=3DSqlgrey;host=3Dlocalhost
> >
> > Cluopd it be the same problem?
> > How can i do it with mysql?
> > I got this:
> >
> > character set latin1=20
> >
> > character sets latin1 big5 czech euc_kr gb2312 gbk=20
> > latin1_de sjis tis620 ujis dec8 dos german1 hp8 koi8_ru=20
> > latin2 swe7 usa7 cp1251 danish hebrew win1251 estonia hungarian=20
> > koi8_ukr win1251ukr greek win1250 croat cp1257 latin5=20
> >
> >
> >  =20
> >> -----Original Message-----
> >> From: sql...@li...=20
> >> [mailto:sql...@li...] On=20
> >> Behalf Of Dan Faerch
> >> Sent: Thursday, January 11, 2007 17:03
> >> To: SQLgrey users mailing-list
> >> Subject: Re: [Sqlgrey-users] Sqlgrey dies while creating=20
> mysql tables
> >>
> >>
> >> Ahh yes...
> >>
> >> Lionel helped someone not long ago who had problems, and it=20
> >> turned out=20
> >> to be a UNICODE problem. Here's a quote from the mailing list:
> >>
> >> "Hum, did you try to use a database with ASCII instead of UNICODE?
> >> SQLgrey doesn't try to speak utf-8 with the database but only=20
> >> pure ASCII."
> >>
> >> Andrew wrote a helpfull mail on how to migrate to ASCII.
> >>  From the maillinglist archives:
> >> http://sourceforge.net/mailarchive/message.php?msg_id=3D37802061
> >>
> >>
> >> On a side note. Since more ppl will have this problem, im=20
> thinking we=20
> >> should either support other encodings or at least warn on=20
> >> execution of=20
> >> sqlgrey.
> >>
> >> Anyone got some thoughts about either of theese?
> >> - How hard is it to support all encodings
> >> - How do we detect if database is ASCII
> >>
> >> If we get a real simple solution, ill try and implement it=20
> very soon.
> >>
> >> - Dan
> >>
> >>
> >> Juraj Variny wrote:
> >>    =20
> >>> Hello,
> >>>
> >>>  perl -MDBI -le 'my=20
> >>>      =20
> >> =
$db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> >> myuser","mypass",undef) or die=20
> "Error:$DBI::errstr".$db->disconnect()'
> >>    =20
> >>>  passed without failure and output nothing. Then I tried to=20
> >>>      =20
> >> create the table, with very interesting result:
> >>    =20
> >>> perl -MDBI -le 'my=20
> >>>      =20
> >> =
$db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> >> u_sqlgrey","greysql",undef); $db->do("CREATE TABLE from_awl=20
> >> (sender_name varchar(64) NOT NULL, sender_domain varchar(255)=20
> >> NOT NULL, src varchar(39) NOT NULL, first_seen timestamp NOT=20
> >> NULL, last_seen timestamp NOT NULL, PRIMARY KEY (src,=20
> >> sender_domain, sender_name))");$db->disconnect();'
> >>    =20
> >>> DBD::mysql::db do failed: Specified key was too long; max=20
> >>>      =20
> >> key length is 1000 bytes at -e line 1.
> >>    =20
> >>> According to http://bugs.mysql.com/bug.php?id=3D4541 , it=20
> >>>      =20
> >> seems the culprit is that I have utf8 database....
> >>    =20
> >>> Juraj
> >>>
> >>> On Wednesday 10 January 2007 20:57, Winfried Neessen wrote:
> >>> (snip)
> >>>  =20
> >>>      =20
> >>>> `---
> >>>> please open a shell an execute this line an send us what=20
> >>>>        =20
> >> error that is
> >>    =20
> >>>> returned by it:
> >>>>
> >>>> ,---
> >>>>
> >>>> | perl -MDBI -le 'my
> >>>> |=20
> >>>>        =20
> >> =
$db=3DDBI->connect("DBI:mysql:database=3Dsqlgrey;host=3Dlocalhost","
> >> youruser","
> >>    =20
> >>>> |yourpass",undef) or die "Error: $DBI::errstr"$db->disconnect()'
> >>>>
> >>>> `---
> >>>>
> >>>> Regards
> >>>> Winfried
> >>>>    =20
> >>>>        =20
> >>>      =20
> >> --------------------------------------------------------------
> >> -----------
> >>    =20
> >>> Take Surveys. Earn Cash. Influence the Future of IT
> >>> Join SourceForge.net's Techsay panel and you'll get the=20
> >>>      =20
> >> chance to share your
> >>    =20
> >>> opinions on IT & business topics through brief surveys -=20
> >>>      =20
> >> and earn cash
> >>    =20
> >> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
> >>    =20
> > &CID=3DDEVDEV
> >  =20
> >> _______________________________________________
> >> Sqlgrey-users mailing list
> >> Sql...@li...
> >> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
> >>
> >>  =20
> >>    =20
> >
> >
> >=20
> --------------------------------------------------------------
> -----------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the=20
> chance to share your
> > opinions on IT & business topics through brief surveys -=20
> and earn cash
> >=20
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge
&CID=3DDEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>
>
> =
-------------------------------------------------------------------------=

> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to =
share
your
> opinions on IT & business topics through brief surveys - and earn cash
> =
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Sqlgrey-users mailing list
> Sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlgrey-users
>
>  =20


-------------------------------------------------------------------------=

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share =
your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
_______________________________________________
Sqlgrey-users mailing list
Sql...@li...
https://lists.sourceforge.net/lists/listinfo/sqlgrey-users