MySQL 3.23.46 but I don't think it did anything because the tables
did not change before and after running the script.
am I missing something ?
Hard to say. I do not remember all details from this development. I
suspect, something was missing in 3.23.x series at all. Can you try
latest 4.0.
thank you very much !!!
I will try 4.0 then
tommy
From: Tonu Samuel <[EMAIL PROTECTED]>
To: tommy liu <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: problem setting up DES_ENCRYPT on MySQL 3.23.46
Date: 07 Mar 2003 16:04:19 +0200
On Thu, 2003-03-06 at 17:52, tommy liu wrote
On Thu, 2003-03-06 at 17:52, tommy liu wrote:
> anyways, yes I did run
> # ./configure --with-vio --with-openssl --prefix=/usr/local/mysql
> and also tried the max version
>
> I also ran mysql_fix_privilege_tables.sh (one along 3.23.46 source)because
> we have MySQL 3.23.46 bu
23.46 source)because
we have MySQL 3.23.46 but I don't think it did anything because the tables
did not change before and after running the script.
am I missing something ?
thank you
Tommy
From: Tonu Samuel <[EMAIL PROTECTED]>
To: tommy liu <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED
Hello
Thanks for a great tool !
and thank you very much in advance for any help
Description:
I am a Programmer working with patient data and for privacy reasons I have
been trying to get des_encrypt() to work on MySQL 3.23.46 with
openssl-0.9.6b on a Linux server.
I followed the steps described
Dear All,
I having issues with MySQL on Linux corrupting our MYD and MYI files
frequently.
We get errors such as "Can't open file: 'TABLE.MYD' which tells me the table
data is corrupt/damaged.
I can rebuild the index and recover the data correctly but this is the 2nd
time in 2 weeks that this ha
ttings (e.g.,
> > key_buffer_size=2G), mysql operates correctly. Additionally, "mysqladmin
> > variables" shows a correct key_buffer value.
> >
> > System memory is not a constraint ( 6 G real memory and 14.5 G swap).
>
> Hi!
>
> This is a problem that we wo
hi!
> "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes:
Sinisa> Albert Chin writes:
>>
>> $ grep SIZEOF_LONG config.h
>> #define SIZEOF_LONG 8
>> #define SIZEOF_LONG_LONG 8
>>
>> $ grep SIZEOF_LONG incldue/my_config.h
>> #define SIZEOF_LONG 8
>> #define SIZEOF_LONG_LONG 8
>>
>>
On Wed, Feb 06, 2002 at 07:17:13PM +0200, Sinisa Milivojevic wrote:
> Albert Chin writes:
> >
> > $ grep SIZEOF_LONG config.h
> > #define SIZEOF_LONG 8
> > #define SIZEOF_LONG_LONG 8
> >
> > $ grep SIZEOF_LONG incldue/my_config.h
> > #define SIZEOF_LONG 8
> > #define SIZEOF_LONG_LONG 8
> >
> >
Albert Chin writes:
>
> Ok. Guess we'll wait for a fix. Any idea when a fix for MySQL will be
> available?
>
> --
> albert chin ([EMAIL PROTECTED])
>
Just look into Changelog's of the versions that come out.
--
Regards,
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Mr. Sinisa M
On Wed, Feb 06, 2002 at 06:12:22PM +0200, Sinisa Milivojevic wrote:
> Albert Chin writes:
> >
> > MySQL 3.23.46 was built with the Sun C++ compiler:
> > $ CC -V
> > CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-03 2001/10/19
> >
> > It was built
Albert Chin writes:
> On Wed, Feb 06, 2002 at 07:17:13PM +0200, Sinisa Milivojevic wrote:
> Yes, SIZEOF_INT is 4:
> $ grep SIZEOF_INT config.h
> #define SIZEOF_INT 4
> $ grep SIZEOF_INT include/my_config.h
> #define SIZEOF_INT 4
>
> However, according to
>
>http://docs.sun.com/ab2/coll.4
Albert Chin writes:
> On Wed, Feb 06, 2002 at 07:17:13PM +0200, Sinisa Milivojevic wrote:
>
> Yes, SIZEOF_INT is 4:
> $ grep SIZEOF_INT config.h
> #define SIZEOF_INT 4
> $ grep SIZEOF_INT include/my_config.h
> #define SIZEOF_INT 4
>
> --
> albert chin ([EMAIL PROTECTED])
>
We shall ha
Albert Chin writes:
>
> $ grep SIZEOF_LONG config.h
> #define SIZEOF_LONG 8
> #define SIZEOF_LONG_LONG 8
>
> $ grep SIZEOF_LONG incldue/my_config.h
> #define SIZEOF_LONG 8
> #define SIZEOF_LONG_LONG 8
>
> --
> albert chin ([EMAIL PROTECTED])
>
If SIZEOF_INT is 4, then it could be our bug.
P
On Wed, Feb 06, 2002 at 08:04:23PM +0200, Sinisa Milivojevic wrote:
> Albert Chin writes:
> > On Wed, Feb 06, 2002 at 07:17:13PM +0200, Sinisa Milivojevic wrote:
> > Yes, SIZEOF_INT is 4:
> > $ grep SIZEOF_INT config.h
> > #define SIZEOF_INT 4
> > $ grep SIZEOF_INT include/my_config.h
> >
hi!
> "Sinisa" == Sinisa Milivojevic <[EMAIL PROTECTED]> writes:
Sinisa> Albert Chin writes:
>>
>> $ grep SIZEOF_LONG config.h
>> #define SIZEOF_LONG 8
>> #define SIZEOF_LONG_LONG 8
>>
>> $ grep SIZEOF_LONG incldue/my_config.h
>> #define SIZEOF_LONG 8
>> #define SIZEOF_LONG_LONG 8
>>
>>
Albert Chin writes:
>
> Ok. Guess we'll wait for a fix. Any idea when a fix for MySQL will be
> available?
>
> --
> albert chin ([EMAIL PROTECTED])
>
Just look into Changelog's of the versions that come out.
--
Regards,
__ ___ ___ __
/ |/ /_ __/ __/ __ \/ /Mr. Sinisa M
On Wed, Feb 06, 2002 at 08:04:23PM +0200, Sinisa Milivojevic wrote:
> Albert Chin writes:
> > On Wed, Feb 06, 2002 at 07:17:13PM +0200, Sinisa Milivojevic wrote:
> > Yes, SIZEOF_INT is 4:
> > $ grep SIZEOF_INT config.h
> > #define SIZEOF_INT 4
> > $ grep SIZEOF_INT include/my_config.h
> >
On Wed, Feb 06, 2002 at 07:17:13PM +0200, Sinisa Milivojevic wrote:
> Albert Chin writes:
> >
> > $ grep SIZEOF_LONG config.h
> > #define SIZEOF_LONG 8
> > #define SIZEOF_LONG_LONG 8
> >
> > $ grep SIZEOF_LONG incldue/my_config.h
> > #define SIZEOF_LONG 8
> > #define SIZEOF_LONG_LONG 8
> >
> >
Albert Chin writes:
> On Wed, Feb 06, 2002 at 07:17:13PM +0200, Sinisa Milivojevic wrote:
> Yes, SIZEOF_INT is 4:
> $ grep SIZEOF_INT config.h
> #define SIZEOF_INT 4
> $ grep SIZEOF_INT include/my_config.h
> #define SIZEOF_INT 4
>
> However, according to
>
>http://docs.sun.com/ab2/coll.4
Albert Chin writes:
> On Wed, Feb 06, 2002 at 07:17:13PM +0200, Sinisa Milivojevic wrote:
>
> Yes, SIZEOF_INT is 4:
> $ grep SIZEOF_INT config.h
> #define SIZEOF_INT 4
> $ grep SIZEOF_INT include/my_config.h
> #define SIZEOF_INT 4
>
> --
> albert chin ([EMAIL PROTECTED])
>
We shall ha
Albert Chin writes:
>
> $ grep SIZEOF_LONG config.h
> #define SIZEOF_LONG 8
> #define SIZEOF_LONG_LONG 8
>
> $ grep SIZEOF_LONG incldue/my_config.h
> #define SIZEOF_LONG 8
> #define SIZEOF_LONG_LONG 8
>
> --
> albert chin ([EMAIL PROTECTED])
>
If SIZEOF_INT is 4, then it could be our bug.
P
On Wed, Feb 06, 2002 at 06:12:22PM +0200, Sinisa Milivojevic wrote:
> Albert Chin writes:
> >
> > MySQL 3.23.46 was built with the Sun C++ compiler:
> > $ CC -V
> > CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-03 2001/10/19
> >
> > It was built
Albert Chin writes:
>
> MySQL 3.23.46 was built with the Sun C++ compiler:
> $ CC -V
> CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-03 2001/10/19
>
> It was built as follows:
> CC=cc CFLAGS="-mr -Qn -xstrconst -xO2 -xtarget=generic -xarch=v9" \
>
ttings (e.g.,
> > key_buffer_size=2G), mysql operates correctly. Additionally, "mysqladmin
> > variables" shows a correct key_buffer value.
> >
> > System memory is not a constraint ( 6 G real memory and 14.5 G swap).
>
> Hi!
>
> This is a problem that we wo
Franklin, Kevin writes:
> We are running an extremely large instance of mysql version 3.23.46 on
> Solaris 2.8. We are attempting to use a software version compiled 64 bit
> and have been experiencing memory related server crashes.
>
> The behavior suggests that we are still unable to use more
We are running an extremely large instance of mysql version 3.23.46 on
Solaris 2.8. We are attempting to use a software version compiled 64 bit
and have been experiencing memory related server crashes.
The behavior suggests that we are still unable to use more than 4G of
memory.
If the server
Emmanuel,
Tuesday, January 22, 2002, 12:05:54 AM, you wrote:
EvdM> However, please advise whether I can run 3.23 and 4.0.1 interchanging on
EvdM> same data without putting the data at risk? BTW, I use InnoDb.
If you exchange data with mysqldump - I believe there will be no problem. But if you
manuel van der Meulen [mailto:[EMAIL PROTECTED]]
> Sent: 21 January 2002 22:57
> To: MySQL General List
> Subject: MySQL 3.23.46 -> 4.01
>
>
> Hello all,
>
> Could someone please advise what is further required to upgrade
> from 3.23.46 -> 4.0.01. Here are the steps I
Hello all,
Could someone please advise what is further required to upgrade from
3.23.46 -> 4.0.01. Here are the steps I followed;
1. Download mysql-4.0.1-alpha-win.zip
2. unzipped
3. ran set-up & installed into d:\mysql-4.0.1\
4. start mysql-max with a bat file, maxstart and this is what ha
I can report a major crash, when entering passwords and mail it to the
list as written in the file "mysqlbug".
If you are interested please read the following lines and the .crash.log
(perhaps you can give me a hint what could have been wrong):
I am working with an Apple PowerBook G3 with MacO
d the form and when I press 'e' to edit again, nothing
> appends and I loose everything. After having filled the form and loosed
> everything 2 times, I decided to send you directly the file that Emacs
> saved in /tmp).
>
> >Description:
> ./configure of mysq
7; to edit again, nothing
appends and I loose everything. After having filled the form and loosed
everything 2 times, I decided to send you directly the file that Emacs
saved in /tmp).
>Description:
./configure of mysql-3.23.46 fails with gcc-3.0.3
>How-To-Repeat:
1) Install Li
hared
> -O3 -tune-host' ./configure --with-libwrap
> --with-mysqld-ldflags=-all-static --enable-assembler
> --prefix=/usr/local/mysql-3.23.46 --with-charset=latin1 --enable-thread-safe-client
>--disable-shared
>
> I have problems linking against -lpthread. There's /usr/
lags=-all-static --enable-assembler
--prefix=/usr/local/mysql-3.23.46 --with-charset=latin1 --enable-thread-safe-client
--disable-shared
I have problems linking against -lpthread. There's /usr/shlib/libpthread.so
Configure thinks DEC threads are installed, so it bumps at the libm.a, but
in
We're having severe problems here. We've been running 2.23.3 on Redhat 6.2
for a while and all has been well. I've also installed mysql several times
with no issues. We had a hard drive go out today, and since then we have not
been able to get mysql to successfully start and accept connections. Ty
Ziying Sherwin <[EMAIL PROTECTED]> writes:
> We are interested in installing MySQL 3.23.46 from source on our Solaris
> 2.8 machine. However, we could not find berkeley DB 3.2.9a that is
> required by MySQL package. Does anyone know where to find it? Thanks.
>
> Since I a
We are interested in installing MySQL 3.23.46 from source on our Solaris
2.8 machine. However, we could not find berkeley DB 3.2.9a that is
required by MySQL package. Does anyone know where to find it? Thanks.
Since I am not on this mailing list, please send the reply to
[EMAIL PROTECTED
Hi.
On Mon, Dec 03, 2001 at 09:39:22PM +0800, [EMAIL PROTECTED] wrote:
> Hello,
>
> I want to know does MySQL 3.23.46 is good for work with Red Hat 6.2 ?
You keep asking this question (which MySQL version to use with RH)
again and again and several people already answered on the
Hello,
I want to know does MySQL 3.23.46 is good for work with Red Hat 6.2 ?
My means is the version ( 3.23.46 ) no any bug with RH 6.2 ?
Is there a new version 3.23.47 / 48 will be producted ?
Thank for your help !
Edward
Hi!
MySQL 3.23.46 is now released.
This is a bug fix release that fixes some newly detected bugs in
MySQL.
If you haven't noticed any problems with your MySQL version and you
don't have a batch that automaticly does ANALYZE TABLE once in a while
there is need to upgrade.
This rele
41 matches
Mail list logo
