Ladies, gentlemen,
Upscene Productions is proud to announce the next
version of the popular multi-DBMS development tool:
" Database Workbench 4.0.1 Pro "
Version 4 introduced full Unicode support, 4.0.1 fixes some issues
found in that initial release, like MySQL Stored Procedures
ing for options in ./configure
./configure --prefix=/opt/mysql --enable-thread-safe-client
--enable-local-infile
Compiling MySQL-4.1.14 on HP-UX using GCC-4.0.1 fails with the linker error:
/usr/ccs/bin/ld: Unsatisfied symbols:
Rotate_log_event::is_valid() (first referenced in slave.o) (data
On 09/23/2004 11:11 AM, Stembridge, Michael <[EMAIL PROTECTED]> wrote:
>>> Without recompiling, is there a way to upgrade the bundled client?
>>
>> No - I believe you need to recompile PHP (this path assumes an RPM
>> installation of MySQL):
>
> Yes, MySQL is installed via RPM.
>
> So, when I r
Stembridge, Michael wrote:
So I assume the version of MySQL bundled with PHP 4.3.1 is in fact
3.23.49
and this is overriding my standalone installation.
It's not overriding anything, it's doing what you asked: in your configure
you told PHP to use its built-in (MYSQL_MODULE_TYPE) MySQL support.
Wi
> > So I assume the version of MySQL bundled with PHP 4.3.1 is in fact
> 3.23.49
> > and this is overriding my standalone installation.
>
> It's not overriding anything, it's doing what you asked: in your configure
> you told PHP to use its built-in (MYSQL_MODULE_TYPE) MySQL support.
>
> > Withou
lue
>
> However, issuing 'mysql -V' at the command line returns version 4.0.1.
>
>
> So I assume the version of MySQL bundled with PHP 4.3.1 is in fact 3.23.49
> and this is overriding my standalone installation.
It's not overriding anything, it's doing wha
ver, issuing 'mysql -V' at the command line returns version 4.0.1.
>
>
> So I assume the version of MySQL bundled with PHP 4.3.1 is in fact 3.23.49
> and this is overriding my standalone installation.
>
> Without recompiling, is there a way to upgrade the bundled client?
ns version 4.0.1.
So I assume the version of MySQL bundled with PHP 4.3.1 is in fact 3.23.49
and this is overriding my standalone installation.
Without recompiling, is there a way to upgrade the bundled client?
Thanks!
--
MySQL General Mailing List
For list archives: http://lists.mysql.co
"Morten Gulbrandsen" <[EMAIL PROTECTED]> wrote:
> 7.5.5.2 Foreign Key Constraints
>
> Hi programmers,
>
> I try to code this
>
> CREATE TABLE EMPLOYEE
> (
> FNAME VARCHAR(15) NOT NULL,
> MINIT CHAR,
> LNAME VARCHAR(15) NOT NULL,
> SSN
7.5.5.2 Foreign Key Constraints
Hi programmers,
I try to code this
CREATE TABLE EMPLOYEE
(
FNAME VARCHAR(15) NOT NULL,
MINIT CHAR,
LNAME VARCHAR(15) NOT NULL,
SSN CHAR(9) NOT NULL,
BDATE DATE,
ADDRESS VARCHAR(30),
SE
Currently I'm using 4.0.1 Alpha and I'm thinking of upgrading to 4.0.5
as I want to be able to issue UPDATE queries that span multiple tables.
Is there anything in particular I should know of or be aware of before
installing 4.0.5? What is the proper procedure for upgrading? Shou
On Wednesday 11 December 2002 01:46, Christopher M. Keslin wrote:
> The following sql query works very well in version 4.0.1-alpha-nt. However
> it returns a null set with the data provided in aBetterLimo.sql in all
> later versions (the last one tried was 4.0.5-beta. I hope tha
Hello,
The following sql query works very well in version 4.0.1-alpha-nt. However
it returns a null set with the data provided in aBetterLimo.sql in all later
versions (the last one tried was 4.0.5-beta. I hope that this is enough
information. If you would like anymore please feel free to
áÌÅËÓÁÎÄÒ,
Monday, August 19, 2002, 2:49:58 PM, you wrote:
áó> ___
áó> MySQL version 4.0.1-alpha on Win 2000 Server SP2 Rus
áó> ___
áó> # The MySQL server
áó> [mysqld]
áó> port=3306
áó> #
uot;áÌÅËÓÁÎÄÒ óÔÅÐÁÎÅÎËÏ"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Monday, August 19, 2002 11:47 AM
Subject: BUG in 4.0.1 - alpha
> ___
>
> MySQL version 4.0.1-alpha on Win 2000 Server SP2 Rus
> __
___
MySQL version 4.0.1-alpha on Win 2000 Server SP2 Rus
___
# mysql config file.
# This will be passed to all mysql clients
[client]
#password=my_password
port=3306
#socket=MySQL
# Here is entries for some
At 09:38 30/7/2002 -0400, Ray Elenteny wrote:
Hi,
>I just moved from 4.0.1 to 4.0.2 on Windows 2000 and my databases that
>had been accessed through "Windows symbolic links" could no longer be
>accessed. I had to add the use-symbolic-links directive back to my
>my.ini fi
I just moved from 4.0.1 to 4.0.2 on Windows 2000 and my databases that
had been accessed through "Windows symbolic links" could no longer be
accessed. I had to add the use-symbolic-links directive back to my
my.ini file to get them to work?
The docs still state that in MySQL 4.0 th
I am currently trying to insert images which are roughly around 140Mb each
into my database using the data type longblob. The problem I seem to be
having it that I cannot set the max_allowed_packet to go over 67107840. In
my /etc/my.cnf I have the following line:
set-variable= max_allowed_pac
problem.
RV> OS Windows 2000.
I tested it on 4.0.2 and it worked as expected. Seems, this problem was fixed.
As to 4.0.1. it can be fixed by running "mysqladmin shutdown" twice :)
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sp
When mysqld-max-nt.exe is started with options
--console --standalone
and after issuing "mysqladmin -u root shutdown"
mysqld reports a shutdown, but does not exit.
mysqld-max don't have this problem.
OS Windows 2000.
Roman Vorobiev.
e-mail: [EMAIL PROTECTED]
__
I posted a couple of days ago on what appears to be a bug in
drop database of mysql-max-4.0.1-2. Here is a recipe to
see if others are seeing the same problem.
This is on Red Hat Linux 7.2 and is extremely repeatable
nor is it limited to a single linux box (ie. not likely
hardware problem
Any clues? Anyone? I'm stumped here guys.
On 2 Jul 2002 at 18:00, [EMAIL PROTECTED] wrote:
> Hi.
>
> I am trying to install MySQL on BSDI BSD/OS 4.0.1 Kernel #3.
>
> Processor: Cpu-1 = Pentium III (448 MHz) GenuineIntel mdl 7 step 2 type 0, feat
> 387fbff
>
>
Hi.
I am trying to install MySQL on BSDI BSD/OS 4.0.1 Kernel #3.
Processor: Cpu-1 = Pentium III (448 MHz) GenuineIntel mdl 7 step 2 type 0, feat
387fbff
Ram: 128M
I configured using:
CC=gcc CXX=gcc CXXFLAGS=-O ./configure --prefix=/usr/local/mysql --with-extra-
charsets=complex
and ran
Hello,
I've tried to install mysql 4.0.1 Alpha.
The configuration did not give me any error's
The "make" also worked just fine.
But when I run "make test" I get the following error:
ERROR: /down/new/mysql-4.0.1-alpha/mysql-test/var/run/master.pid was not
created
n PHP to pick up these [mysql] client values, I'll be all set.
Hope this has been helpful to someone!
-Clay
> From: Clay Loveless <[EMAIL PROTECTED]>
> Date: Tue, 18 Jun 2002 18:03:02 -0700
> To: MySQL <[EMAIL PROTECTED]>
> Subject: Re: MySQL 4.0.1 & S
A little more information on this problem ...
- Tonu's notes state that there are sample SSL keys & certs for testing
purposes in the "SSL" directory of the mysql tarball. There is no SSL
directory in the mysql-4.0.1-alpha.tar.gz file. Does anyone know which
tarball he
L <[EMAIL PROTECTED]>
> Subject: Re: MySQL 4.0.1 & SSL config - a shot in the dark
>
> Tonu,
>
> Thank you, thank you! The formal documentation effort is apparently still
> underway based on your notes ... The link you included eliminates a lot of
> guesswork! : )
>
Anthony,
Monday, June 17, 2002, 5:13:23 PM, you wrote:
ARJB> I am trying to play with innodb tables in 4.0.1-alpha-max on
ARJB> Solaris 2.7, but I am having a problem with setting up an
ARJB> autoextend tablespace... as soon as I put :autoextend at the
ARJB> end of my innodb_da
Tonu,
Thank you, thank you! The formal documentation effort is apparently still
underway based on your notes ... The link you included eliminates a lot of
guesswork! : )
> This part of MySQL is written by me and I am sure it worked :)
I'm sure it does -- what I meant was that the way I had it c
On Sat, 15 Jun 2002, Clay Loveless wrote:
> I've been trying to figure out how to set up SSL support in mysql-4.0.1 ...
> The online documentation is pretty sparse on the subject.
>
> Here's what I've got so far -- and so far this is *NOT* working. I'm putti
I've been trying to figure out how to set up SSL support in mysql-4.0.1 ...
The online documentation is pretty sparse on the subject.
Here's what I've got so far -- and so far this is *NOT* working. I'm putting
it out here so that someone else may be able to fiddle around o
MySQL. The 'Web access to the MySQL BitKeeper
repository' link in the '1.6.4 Useful MySQL-related links' section of
the MySQL manual seems not to work: "Error 503: Can't find project
root".
>How-To-Repeat:
With a 4.0.1 server and client, execute the f
Hello
MySQL 4.0.1 Solaris 2.7 official binary reproducibly crashes with sig
11 when run in a slave mode and when its master (4.0.1 official Linux
binary) is populated via "mysqlimport" tool from a remote machine.
Here are some interesting log files [edited]:
, $ mysqld --
Hi,
I use MySQL-Max-4.0.1 and i am wantering if
the information about the foreign keys are stored at
comment properties of table with maximum length 60 characters?
I need to use innodb tables with many f.keys.What I have to do?
Thank you
#x27; running 3.23.39 is using character_set latin1
> host 'fidel' running 4.0.1 is using character_set latin1_de
>
> latin1_de is character set '#31' mentioned in the error message below.
> Character set latin_de was introduced with release 4.0.0. From the very
>
-Original Message-
From: victoria papazoi [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 07, 2002 11:58 AM
To: [EMAIL PROTECTED]
Subject: foreign keys in MySQL-Max-4.0.1
Hi,
I use MySQL-Max-4.0.1 and i am wantering if
the information about the foreign keys are stored at
comment
Hi,
I use MySQL-Max-4.0.1 and i am wantering if
the information about the foreign keys are stored at
comment properties of table with maximum length 60 characters?
I need to use innodb tables with many f.keys.What I have to do?
Thank you
ok folks,
I was digging into my own problem and that's what I found:
host 'hegel' running 3.23.39 is using character_set latin1
host 'fidel' running 4.0.1 is using character_set latin1_de
latin1_de is character set '#31' mentioned in the error messag
Hi,
I use MySQL-Max-4.0.1 and i am wantering if
is true that the information about the foreign keys are stored at
comment properties of table with maximum length 60 characters?
I need to use innodb tables with many f.keys.What I have to do?
Thank you
Dear listmembers,
I've got 2 hosts running Linux: hostnames are 'hegel' and 'fidel'
me@hegel:~>mysqladmin version
mysqladmin Ver 8.21 Distrib 3.23.39, for pc-linux-gnu on i586
me@fidel:~>mysqladmin version
mysqladmin Ver 8.23 Distrib 4.0.1-alpha, for pc-linux
From: ymalik
To: [EMAIL PROTECTED]
Subject: [Installation ]
>Description:
mysql-4.0.1-alpha (Official MySQL RPM) installtion problem
>How-To-Repeat:
>Fix:
>Submitter-Id:
>Originator:
>Organization:
>MySQL support: [none | licence | email sup
Yogesh,
Tuesday, June 04, 2002, 12:26:10 PM, you wrote:
YM> >Description:
YM>
YM> mysql-4.0.1-alpha (Official MySQL RPM) installtion problem
YM> >How-To-Repeat:
YM>
YM> >Fix:
YM>
YM> >Submitter-Id:
YM> >Originator:
YM> &g
From: ymalik
To: [EMAIL PROTECTED]
Subject: [Installation ]
>Description:
mysql-4.0.1-alpha (Official MySQL RPM) installtion problem
>How-To-Repeat:
>Fix:
>Submitter-Id:
>Originator:
>Organization:
>MySQL support: [none | licence | email sup
Leeuw van der, Tim writes:
> Hello,
>
> Thank you very much for your reply! I was hoping that this was indeed fixed
> in 4.0.2. I was using 4.0.0 when the bug occurred and upgraded today to
> 4.0.1; I will retest the query with 4.0.2 as soon as it's released.
>
Patrik,
Friday, May 31, 2002, 2:22:10 AM, you wrote:
PB> I suspect that there might be a bug in the LOAD DATA and SOURCE statements
PB> of MySQL-4.0.1-2 (alpha), but since I'm not 100% sure, I am sending this
PB> to the list and maybe someone else migt be able to reprod
Hi!
I suspect that there might be a bug in the LOAD DATA and SOURCE statements
of MySQL-4.0.1-2 (alpha), but since I'm not 100% sure, I am sending this
to the list and maybe someone else migt be able to reproduce...
My configuration:
RedHat Linux 7.3 on i686
MySQL-4.0.1-2 server+client
not that
big, since it is only 226 byte.
It also suggests that I should check the uptime of the mysqld, so I can
verify that it hasn't crashed.
issuing the 'mysqladmin version' command gives this:
Server version 4.0.1-alpha
Protocol version10
Connection
ROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, May 23, 2002 5:15 AM
Subject: Re: 4.0.1 Bugs
>
> I had problems with unions that result in large queries too.
> I found that MySQL 4 was using Heap tables for Unions.
> One can Increase the Heap Table size to help, but
>
p://www.innodb.com for the online manual and latest news on InnoDB
> >
> > - Original Message -
> > From: "Richard Clarke" <[EMAIL PROTECTED]>
> > To: "Heikki Tuuri" <[EMAIL PROTECTED]>
> > Sent: Sunday, May 19, 2002 12:02 PM
&
EMAIL PROTECTED]>
> To: "Heikki Tuuri" <[EMAIL PROTECTED]>
> Sent: Sunday, May 19, 2002 12:02 PM
> Subject: Re: 4.0.1 Bugs
>
>
> > Heikki,
> > As for my crashes. This one is a little hard, see, we have two
> machines
> > that do this. Both however
On Tue, 21 May 2002, Michael Widenius wrote:
>
> Hi!
>
> >>>>> "Michael" == Michael B Venezia <[EMAIL PROTECTED]> writes:
>
> >> Description:
> Michael> Possible Bug in UPDATE in MySQL 4.0.1
>
>
>
> Michael
Hi!
>>>>> "Michael" == Michael B Venezia <[EMAIL PROTECTED]> writes:
>> Description:
Michael> Possible Bug in UPDATE in MySQL 4.0.1
Michael> Attempting backtrace. You can use the following information to find out
Michael> where
Michael,
Sunday, May 19, 2002, 12:56:00 PM, you wrote:
MBV> Description:
MBV> Possible Bug in UPDATE in MySQL 4.0.1
MBV> The following is the message in the error log...
MBV> Number of processes running now: 0
MBV> 020519 04:55:30 mysqld restarted
MBV> 02051
manual and latest news on InnoDB
- Original Message -
From: "Richard Clarke" <[EMAIL PROTECTED]>
To: "MYSQL" <[EMAIL PROTECTED]>; "Heikki Tuuri"
<[EMAIL PROTECTED]>
Sent: Sunday, May 19, 2002 3:25 PM
Subject: Re: 4.0.1 Bugs
> Heikki,
"Heikki Tuuri" <[EMAIL PROTECTED]>
To: "Richard Clarke" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Sunday, May 19, 2002 1:01 PM
Subject: Re: 4.0.1 Bugs
> Richard,
>
> the assertion failure below is very probably caused by the SHOW CREATE
TAB
Richard,
the assertion failure below is very probably caused by the SHOW CREATE TABLE
memory corruption bug which was fixed in 3.23.48, but not yet in 4.0.1. It
is usually caused by mysqldump. The regularity of the crashes suggests they
might be connected to mysqldumps.
If the memory
Richard,
the assertion failure below is very probably caused by the SHOW CREATE TABLE
memory corruption bug which was fixed in 3.23.48, but not yet in 4.0.1. It
is usually caused by mysqldump. The regularity of the crashes suggests they
might be connected to mysqldumps.
If the memory
>Description:
Possible Bug in UPDATE in MySQL 4.0.1
The following is the message in the error log...
Number of processes running now: 0
020519 04:55:30 mysqld restarted
020519 4:55:30 InnoDB: Started
/usr/local/mysql/bin/mysqld: ready for connections
mysqld got signal
Richard,
can you upload via ftp gzipped dumps of the two tables in the UNION to
/pub/mysql/secret at support.mysql.com?
About the crashes which occur in 5 - 7 days: please send me the error log
of MySQL 'hostname'.err so that I can resolve the stack dumps, if they
exist. 4.0.1 is
ginal Message -
From: "Carsten Gehling" <[EMAIL PROTECTED]>
To: "Richard Clarke" <[EMAIL PROTECTED]>; "MYSQL" <[EMAIL PROTECTED]>
Sent: Saturday, May 18, 2002 9:48 PM
Subject: SV: 4.0.1 Bugs
> > Fra: Richard Clarke [mailto:[EMAIL PROTECTED]]
> Fra: Richard Clarke [mailto:[EMAIL PROTECTED]]
> Sendt: 18. maj 2002 22:29
> Emne: 4.0.1 Bugs
>
>
> List,
> I wondered if any movement has been made to determine the cause of the
> following "bugs" that I have come across using Mysql 4.0.1.
>
> 1)
List,
I wondered if any movement has been made to determine the cause of the
following "bugs" that I have come across using Mysql 4.0.1.
1) selectunion causes a temporary table full type error when the
datasets aren't even that large and when there is bags of disk s
Okay, I believe the problem I am having is make is having some problemsis in
libmysql.c when the getenv fucntion is used.
I commented out the following lines in libmysql.c and then the program errored in the
next line with getenv. Anyone have a workaround for this code on HP-UX 11.00?
if (!p
I am trying to build mysql-4.0.1 from the source...
When it gets to libtool it is having problems finding gcc... How can I cahnge the
path to the full path of the gcc compiler?
Thanks,
Taylor
Taylor Lewick
Unix System Administrator
Fortis Benefits
816 881 6073
"Help Wanted. Seeking Tel
Hi all, I am attempting to build mysql-4.0.1-alpha on an HP-UX 11.00 box because the
binary I installed worked,
but I couldnet connect to the database by typing in a password at the prompt, I had to
actually pass it on the command line.
I figured there might be a few other odd behaviors that
Hi!
On May 06, Gurhan Ozen wrote:
>Is there anyway to see what bugs have been reported for fulltext search
> in 4.0.1 alpha ? I know that Jeremy Zawodny has mentioned that a few bugs
> were found in fulltext search in 4.0.1 , but didn't tell what they were.
> I have instal
Is there anyway to see what bugs have been reported for fulltext search
in 4.0.1 alpha ? I know that Jeremy Zawodny has mentioned that a few bugs
were found in fulltext search in 4.0.1 , but didn't tell what they were.
I have installed 4.0.1 and ran it as second mysqld in my web s
My new webhost has these two mysql servers installed:
MySQL 3.23.46
MySQL 4.0.1 alpha
which I am going to choose between...
(They say they first installed the alpha just for testing because some
customers requested it, but then kept it because they then thought it
was quite stable)
The best
Nick,
Thursday, April 25, 2002, 11:16:02 PM, you wrote:
NG> Egor Egorov wrote:
>>Hm ... I tested .. it works fine for me ...
>>What error did you get when your user tried to lock tables?
NG> Here is the error message:
NG> Error
NG> SQL-query :
NG> Lock Table bugs write
NG> MySQL said:
NG> selec
Egor Egorov wrote:
>Nick,
>Wednesday, April 24, 2002, 10:52:28 PM, you wrote:
>
>NG> Nick Gilliam wrote:
>
>>>Egor Egorov wrote:
>>>
>>>>NG> I have encountered a problem with MySQL 4.0.0 and 4.0.1 in which
>>>>I am NG> unable
Nick,
Wednesday, April 24, 2002, 10:52:28 PM, you wrote:
NG> Nick Gilliam wrote:
>> Egor Egorov wrote:
>>> NG> I have encountered a problem with MySQL 4.0.0 and 4.0.1 in which
>>> I am NG> unable to bet a lock on a table with any userid except root.
>>&
Nick Gilliam wrote:
>
>
> Egor Egorov wrote:
>
>> Nick,
>> Wednesday, April 24, 2002, 3:59:26 PM, you wrote:
>>
>> NG> I have encountered a problem with MySQL 4.0.0 and 4.0.1 in which
>> I am NG> unable to bet a lock on a table with any user
Egor Egorov wrote:
>Nick,
>Wednesday, April 24, 2002, 3:59:26 PM, you wrote:
>
>NG> I have encountered a problem with MySQL 4.0.0 and 4.0.1 in which I am
>NG> unable to bet a lock on a table with any userid except root.
>
>NG> Here is my environment:
>NG>
Nick,
Wednesday, April 24, 2002, 3:59:26 PM, you wrote:
NG> I have encountered a problem with MySQL 4.0.0 and 4.0.1 in which I am
NG> unable to bet a lock on a table with any userid except root.
NG> Here is my environment:
NG> Sun 450
NG> Solaris 2.8
NG> MyISAM tables
NG
I have encountered a problem with MySQL 4.0.0 and 4.0.1 in which I am
unable to bet a lock on a table with any userid except root.
Here is my environment:
Sun 450
Solaris 2.8
MyISAM tables
Any ideas on how this problem could be solved?
Thanks,
Nick Gilliam
Richard,
- Original Message -
From: ""Richard Harms"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.mysql
Sent: Monday, April 22, 2002 2:32 AM
Subject: InnoDB Error 150, MySQL 4.0.1 alpha & 3.23.49
> Hello,
>
> When attempting to create some
Hello,
When attempting to create some tables using the MySQL 4.0.1 alpha and
3.23.49, I'm getting a generic error message, "General error: Can't
create table './industria/ORDEREDITEMS.frm' (errno: 150)." The other 6
tables, all using similar features, are created
On Fri, Apr 19, 2002 at 04:12:35AM -0700, Jeremy Zawodny wrote:
> On Wed, Apr 10, 2002 at 08:48:01AM -0700, Nick Pasich wrote:
>
> [snip]
>
> >
> > Any subsequent executions do not. This is because of query caching.
> > I can run --> mysql -e "reset query cache" <-- which will enable
>
On Wed, Apr 10, 2002 at 08:48:01AM -0700, Nick Pasich wrote:
[snip]
>
> Any subsequent executions do not. This is because of query caching.
> I can run --> mysql -e "reset query cache" <-- which will enable
> the next call to mysqldump to write data.
>
> I believe that
el' or any other word it works flawlessy. I have written the queries
like this since '... against ('+windows +excel' IN BOOLEAN MODE)' doesn't
work in the 4.0.1 version of MySQL.
I find this pretty strange
>From mysql consol:
mysql> SELECT count(*) FROM DB_GN
On Wed, Apr 10, 2002 at 10:06:47AM -0700, [EMAIL PROTECTED] wrote:
>
> Can anyone comment on the stability of the current 4.x MySQL
> release.
>
> I'd be using MyISAM tables and only features which are currently
> available in the 3.23.x series.
For my purposes, the 4.0.x builds I've used are j
Can anyone comment on the stability of the current 4.x MySQL release.
I'd be using MyISAM tables and only features which are currently
available in the 3.23.x series.
--
do svidaniya,
~mitch
-
Before posting, please check
>Description:
I'm using Mysql 4.0.1 with query caching:
set-variable = query_cache_limit=10M
set-variable = query_cache_size=10M
set-variable = query_cache_startup_type=1
The Command:
mysqldump
> Adriano Manocchia wrote:
> Well, first off, I can't seem to get max_allowed_packet higher than 64
> MB on the server using 3.23.x or 4.0.1. Changes made to /etc/my.cnf are
> reflected in the system settings, but only up to 64 MB, then regardless
> of what I put in ther
Well, first off, I can't seem to get max_allowed_packet higher than 64
MB on the server using 3.23.x or 4.0.1. Changes made to /etc/my.cnf are
reflected in the system settings, but only up to 64 MB, then regardless
of what I put in there, it stays at 64 MB. But like I said, the file is
) into a DB successfully, but now I need to do it with a 34 MB BLOB,
AM> so I upgraded to MySQL 4.0.1. First off, I can't get
AM> max_allowable_packet to go higher than 64M, regardless of what I set it
AM> to, but that shouldn't be the problem, right? But I still keep getting
AM&
It sounds to me that you're exceeding the maximum packet size mysql can
handle.
Adriano Manocchia wrote:
>
> I've been using a perl script to insert a very large blob (up to about 8
> MB) into a DB successfully, but now I need to do it with a 34 MB BLOB,
> so I upgraded
I've been using a perl script to insert a very large blob (up to about 8
MB) into a DB successfully, but now I need to do it with a 34 MB BLOB,
so I upgraded to MySQL 4.0.1. First off, I can't get
max_allowable_packet to go higher than 64M, regardless of what I set it
to, but that
[EMAIL PROTECTED] writes:
> >Description:
>
> Take two tables (call them a and b), which have identical structures. Table a
> has no rows, table b has some (say 10) rows. If you do this:
>
> select * from a union select * from b limit 0,5
>
> It works as expected. Now do this:
>
> select *
SQL support: none
>Synopsis: Union + Limit issue in 4.0.1 Alpha
>Severity: non-critical
>Priority: medium
>Category: mysql
>Class: sw-bug
>Release: mysql-4.0.1-alpha (Official MySQL binary)
>Environment:
System: Linux webserver1 2.4.17 #
Tomasz,
I tested also with mysql-4.0.1 and it worked.
But are you using a non-latin1 character set?
If yes, the bug which was fixed in 3.23.49 might cause the problem.
Did you compile MySQL yourself? If yes, what compiler?
Please download the official MySQL-Max-3.23.49a binary from
At 07:22 2002-03-14, Heikki Tuuri wrote:
>Tomasz,
>
>are you using a non-latin1 character set?
No, didn't change the charset. As You can see from my reply to Victoria
yesterday, will need to, eventually (for different reasons, though, not
books), but right now I am in a proof-of-concept stag
At 01:57 2002-03-14, Heikki Tuuri wrote:
>Tomasz,
>
>are you sure you are running 4.0.1? In the rpm of 4.0.0 there were no
>foreign keys.
>
>I tested this on mysql-max-4.0.1, and it worked.
Well...
[root@flow11 httpd]# mysqladmin -p version
Enter password:
mysqladmin Ver
re in dict0crea.c, reporting an internal error 17.
"
might be the root of your problem with 4.0.1.
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.mysql.com/
Speed up adding of features to MySQL/InnoDB through support contracts
See http://www.innodb.c
Tomasz,
are you sure you are running 4.0.1? In the rpm of 4.0.0 there were no
foreign keys.
I tested this on mysql-max-4.0.1, and it worked.
Best regards,
Heikki Tuuri
Innobase Oy
---
Order technical MySQL/InnoDB support at https://order.mysql.com/
Speed up adding of features to MySQL/InnoDB
At 16:57 2002-03-13, Rick Flower wrote:
>Tomasz writes:
>
>>> >From section 16 of http://www.innodb.com/ibman.html you find detailed
>>>information about every InnoDB version. For example, 4.0.1 == 3.23.47.
>>>
>>>Foreign keys should work in 4.0.1.
Tomasz writes:
>> >From section 16 of http://www.innodb.com/ibman.html you find detailed
>>information about every InnoDB version. For example, 4.0.1 == 3.23.47.
>>
>>Foreign keys should work in 4.0.1.
>Hmmm... That's what I read, too. And after several
. It will probably be out at
>the end of March.
OK, so I can just hang up my hat till then.
> >From section 16 of http://www.innodb.com/ibman.html you find detailed
>information about every InnoDB version. For example, 4.0.1 == 3.23.47.
>
>Foreign keys should work in 4.0.1.
of http://www.innodb.com/ibman.html you find detailed
information about every InnoDB version. For example, 4.0.1 == 3.23.47.
Foreign keys should work in 4.0.1.
"
Starting from version 3.23.50 InnoDB returns the foreign key definitions of
a table when you call
SHOW CREATE TABLE yourtablename
1 - 100 of 183 matches
Mail list logo
