Re: Problems using date with MySQL 4.1.0 - Alpha

2003-12-14 Thread Paul DuBois
At 18:10 -0600 12/14/03, Lenny Sorey wrote: I am currently using MySQL 4.1 Win2K version along ODBC 3.5.1 Driver I am having trouble using the following LOAD DATA INFILE to import a txt, comma delimited file into to a Mysql Table. Actually the only problem is the date field loading into mysql 4.

Problems using date with MySQL 4.1.0 - Alpha

2003-12-14 Thread Lenny Sorey
I am currently using MySQL 4.1 Win2K version along ODBC 3.5.1 Driver I am having trouble using the following LOAD DATA INFILE to import a txt, comma delimited file into to a Mysql Table. Actually the only problem is the date field loading into mysql 4.1. I have defined the field as a date, date

Re: Mysql 4.1.0

2003-12-11 Thread Lenz Grimmer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, On Tue, 9 Dec 2003, Mark Needleman wrote: > Is there anyway to still get the Solaris 9 64 bit binary for version > 4.1.0 - now that 4.1.1 alpha appears to be out the 4.1.0 binaries don't > seem to be available on the download page Yes, older 4.1

Mysql 4.1.0

2003-12-09 Thread Mark Needleman
Is there anyway to still get the Solaris 9 64 bit binary for version 4.1.0 - now that 4.1.1 alpha appears to be out the 4.1.0 binaries don't seem to be available on the download page Thanks Mark Needleman Product Manager - Standards Sirsi Corporation email: [EMAIL PROTECTED] -- MySQL Ge

Upgrade to MySQL 4.1.0-alpha [No Virus found]

2003-10-29 Thread laurent . paul
Hello, I'm trying to upgrade to version 4.1.0-alpha of MySQL from version 3.23.51 on a Windows 2000 platform. I've downloaded the binary distribution of 4.1.0-alpha and followed the install process(README.1st) for an upgrade install. At the step : * Execute the 'mysql_fix_privilege_tables.sq

Mysql 4.1.0 utf8 on linux : maybe known bug and current bk compile problem

2003-09-30 Thread Gilles Magnier
esponses suggest that it's because client session does not use utf8 character set. In my case i'm "sure" both client and server are using utf8. ("status" command report it) So the problem is : Using Mysql 4.1.0-alpha (recompiled rpm) with InnoDb Database and charset utf8

Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions

2003-09-29 Thread Paul DuBois
At 22:05 +0400 9/29/03, G B U wrote: > On Mon, Sep 29, 2003 at 09:33:29PM +0400, G B U wrote: > > Hmm... am I missing something?! IIRC there is nothing manual about Innodb > not supporting spatial extensions. And on windows it seems that all is working > fine. This is from my Win2000 box with

Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions

2003-09-29 Thread Paul DuBois
At 21:33 +0400 9/29/03, G B U wrote: > At 19:16 +0300 9/29/03, Victoria Reznichenko wrote: >"G B U" <[EMAIL PROTECTED]> wrote: >> >> It seems to me that combination from the subject just doesn't work. >> Every time I try to incorporate spatial column into Innodb table >> Mysql dies. The si

Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions

2003-09-29 Thread G B U
> On Mon, Sep 29, 2003 at 09:33:29PM +0400, G B U wrote: > > > > Hmm... am I missing something?! IIRC there is nothing manual about Innodb > > not supporting spatial extensions. And on windows it seems that all is working > > fine. This is from my Win2000 box with the same Mysql version: > > > >

Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions

2003-09-29 Thread Jeremy Zawodny
On Mon, Sep 29, 2003 at 09:33:29PM +0400, G B U wrote: > > Hmm... am I missing something?! IIRC there is nothing manual about Innodb > not supporting spatial extensions. And on windows it seems that all is working > fine. This is from my Win2000 box with the same Mysql version: > > mysql> create

Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions

2003-09-29 Thread G B U
> At 19:16 +0300 9/29/03, Victoria Reznichenko wrote: > >"G B U" <[EMAIL PROTECTED]> wrote: > >> > >> It seems to me that combination from the subject just doesn't work. > >> Every time I try to incorporate spatial column into Innodb table > >> Mysql dies. The simplest case, easy to repeat is be

Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions

2003-09-29 Thread Paul DuBois
At 19:16 +0300 9/29/03, Victoria Reznichenko wrote: "G B U" <[EMAIL PROTECTED]> wrote: It seems to me that combination from the subject just doesn't work. Every time I try to incorporate spatial column into Innodb table Mysql dies. The simplest case, easy to repeat is bellow. When I'm trying to

Re: Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions

2003-09-29 Thread Victoria Reznichenko
"G B U" <[EMAIL PROTECTED]> wrote: > > It seems to me that combination from the subject just doesn't work. > Every time I try to incorporate spatial column into Innodb table > Mysql dies. The simplest case, easy to repeat is bellow. > When I'm trying to create table with just one spatial column

Incompatibility: FreeBSD+MySQL 4.1.0+InnoDB+Spatial Extensions

2003-09-29 Thread G B U
Hi It seems to me that combination from the subject just doesn't work. Every time I try to incorporate spatial column into Innodb table Mysql dies. The simplest case, easy to repeat is bellow. When I'm trying to create table with just one spatial column I'm getting following error: mysql> cre

Re: mysql 4.1.0-alpha and innodb

2003-09-16 Thread Victoria Reznichenko
Odhiambo Washington <[EMAIL PROTECTED]> wrote: > Excuse my dumbness, but how do I tell MySQL server that I need > InnoDB tables, not MyISAM? I was running 4.0.14 and it was ok, > but now when I create a new db in 4.1.0-alpha the tables are > defaulting to MyISAM > > Am I missing some startup optio

mysql 4.1.0-alpha and innodb

2003-09-16 Thread Odhiambo Washington
Excuse my dumbness, but how do I tell MySQL server that I need InnoDB tables, not MyISAM? I was running 4.0.14 and it was ok, but now when I create a new db in 4.1.0-alpha the tables are defaulting to MyISAM Am I missing some startup option? Thanks. -Wash -- Odhiambo Washington <[EMAIL PRO

RE: Link error when using prepared statements in mysql 4.1.0 alph a

2003-09-05 Thread Amit Jindal
: Mark Matthews [mailto:[EMAIL PROTECTED] > Sent: Friday, September 05, 2003 4:55 PM > To: Amit Jindal > Cc: '[EMAIL PROTECTED]' > Subject: Re: Link error when using prepared statements in mysql 4.1.0 > alpha > > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 >

Re: Link error when using prepared statements in mysql 4.1.0 alpha

2003-09-05 Thread Mark Matthews
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Amit Jindal wrote: > Hi, I am trying to use mysql 4.1.0 C client (libmysql.lib) and I am getting > link errors. > I checked the libmysql.lib and it doesn't seems to have these symbols. > > > Linking... > SimpleInsert

Link error when using prepared statements in mysql 4.1.0 alpha

2003-09-05 Thread Amit Jindal
Hi, I am trying to use mysql 4.1.0 C client (libmysql.lib) and I am getting link errors. I checked the libmysql.lib and it doesn't seems to have these symbols. Linking... SimpleInsertSelect.obj : error LNK2001: unresolved external symbol [EMAIL PROTECTED] SimpleInsertSelect.obj : error LN

Link error when using prepared statements in mysql 4.1.0 alpha

2003-09-05 Thread Amit Jindal
Hi, I am trying to use mysql 4.1.0 C client (libmysql.lib) and I am getting link errors. I checked the libmysql.lib and it doesn't seems to have these symbols. Linking... SimpleInsertSelect.obj : error LNK2001: unresolved external symbol [EMAIL PROTECTED] SimpleInsertSelect.obj : error LN

mysql_install_db on Mysql 4.1.0 seg-faults

2003-08-18 Thread Simon
Hi, I'm trying to get a version of MySQL 4.1.0 installed on my (Gentoo Linux) machine. I have a copy of MySQL 4.0.13 already installed, using Gentoo's ebuilds, but am trying to install 4.1.0 in a side-by-side configuration. (Into /usr/local/mysql_alpha, talking to port 3300) - So I c

Re: Delphi 7 and MySQL 4.1.0 alpha

2003-06-09 Thread Veysel Harun Sahin
Did you try to put this dll into your application directory? The common way to use this dll is to hold it together with executable. [EMAIL PROTECTED] wrote: Hello, I'm trying to get connection on MySQL 4.1.0 alpha edition by using the SQLCOnnection (dbExpress) object. I am having the

Delphi 7 and MySQL 4.1.0 alpha

2003-06-09 Thread George Christoforakis
Hello, I'm trying to get connection on MySQL 4.1.0 alpha edition by using the SQLCOnnection (dbExpress) object. I am having the error 'Unable to load libmysql.dll'. I placed this file into the winnt\system32 folder... still didn't work. I put the whole path into the Vendo

Re: passwords in mysql 4.1.0-alpha

2003-06-08 Thread Stefan Hinz
ot;Client don't support the authentication > protocol required by server, consider upgrade client". > What happen The length of the password hash (in the mysql.user Password column) has changed from 16 (MySQL < 4.1.0) to 45 bytes (MySQL 4.1.0). You can still use the old ha

passwords in mysql 4.1.0-alpha

2003-06-07 Thread Renán Aliosha Rojas Siñani
I installed the version 4.1.0-alpha of mysql in Windows XP. At the beginning and in general everything works very well. But I have a problem of incompatibility (I guess). When users are created with passwords, those users cannot be connected. Mysql says: "Client don't support the authentication pro

Problem compiling mysql 4.1.0

2003-05-30 Thread Pierre
Hi, I try to compile mysql-4.1.0-alpha on my GNU/Linux system with gcc-3.2 there was no problem with the configure, but for the make I got this : [...] Making all in cmd-line-utils gmake[2]: Entering directory `/tmp/mysql-4.1.0-alpha/cmd-line-utils' Making all in libedit gmake[3]: Ent

Errors configuring mysql 4.1.0

2003-05-29 Thread Pierre
Hi, I tried to configure mysql-4.1.0 and I got these errors : [...] checking for OpenSSL... yes ./configure: test: =: unary operator expected no ./configure: no: command not found ./configure: no: command not found mkdir: cannot create directory `include/readline': File exists che