Re: mysqld-max startup unusual error

2003-12-29 Thread Egor Egorov
"David W. Brown" <[EMAIL PROTECTED]> wrote: > Hello mysql list, I have recently incurred an unusual error. Attempts to startup > mysqld-max fail with the following error: > > 031226 17:02:08 Error message file 'e:\mysql\share\english\errmsg.sys' had only 192 > error messages, > but it should co

Re: mysqld max

2003-07-09 Thread Paul DuBois
At 9:26 -0500 7/9/03, azamka wrote: Hi I am trying to make mysqld max so i can create innodb tables but I am getting the following error when i run mysqld No Variable Match for: -0 'innodb_buffer_pool_size = 40M' ./mysqld version 3.23.56 for pc-linux on i686 I am unable to figure out what to do. Th

RE: mysqld max

2003-07-09 Thread Rudy Metzger
Please note that InnoDB is included as from MySQL 4.0 in the "standard" release. So the easiest way to use InnoDB would be to grab a RPM or binary distribution and install it on your system. No need to compile one yourself then. However, if for some reasons you must have 3.x or are on a not suppor

Re: mysqld-max-nt.exe as a service

2003-02-23 Thread Stefan Hinz
Rob, > How do I open mysqld-max-nt.exe as a service (so I don't have to see a DOS > console open for it all the time). Here is the command I use to open it > currently: > mysqld-max-nt.exe --console --standalone > Any help would be appreciated! Of the many ways to accomplish this, I prefer this

RE: mysqld-max-nt.exe as a service

2003-02-22 Thread John W. Holmes
> How do I open mysqld-max-nt.exe as a service (so I don't have to see a DOS > console open for it all the time). Here is the command I use to open it > currently: > > mysqld-max-nt.exe --console --standalone > > Any help would be appreciated! The following command: mysqld-max-nt.exe --install

RE: mysqld-max but still no referential integrity?

2003-02-22 Thread Robert Mark Bram
\ibdata Rob :) > -Original Message- > From: Robert Mark Bram [mailto:[EMAIL PROTECTED] > Sent: Sunday, 23 February 2003 1:03 AM > To: Mysql > Subject: RE: mysqld-max but still no referential integrity? > > > Howdy all! > > I have changed my my.ini but my pr

RE: mysqld-max but still no referential integrity?

2003-02-22 Thread Robert Mark Bram
Howdy all! I have changed my my.ini but my problem remains... details below. Any further assistance would be greatly appreciated! I apolagise to all if it seems I am flooding.. :( Rob :) :-> :-} == my.ini [mysqld] basedir=C:/mySql/ datadir=C:/mySql/data [WinMySQLAdmin] Server=C:/mySql/bin/

Closing mysqld-max - was RE: mysqld-max but still no referential integrity?

2003-02-22 Thread Robert Mark Bram
I think I solved this.. I deleted C:\mySql\ibdata and I could start it up again.. I think I know why it happened too.. when I start a connection with this: mysqld-max-nt.exe --console --standalone it takes the console over.. How do I properly close it down from another console? Rob :) ---

RE: mysqld-max but still no referential integrity?

2003-02-22 Thread Robert Mark Bram
Hi Oliver, I tried as you suggested, but I have a different problem now.. > > == my.ini > > My my.ini file: > > > > [mysqld] > > basedir=C:/mySql/ > > datadir=C:/mySql/data > > > > [WinMySQLAdmin] > > Server=C:/mySql/bin/mysqld-MAX-nt.exe > > innodb_data_home_dir = C:\mySql\ibdata > > innodb

Re: mysqld-max but still no referential integrity?

2003-02-22 Thread Oliver Schlag
Hy Rob, > == my.ini > My my.ini file: > > [mysqld] > basedir=C:/mySql/ > datadir=C:/mySql/data > > [WinMySQLAdmin] > Server=C:/mySql/bin/mysqld-MAX-nt.exe > innodb_data_home_dir = C:\mySql\ibdata > innodb_data_file_path=ibdata1:30M:autoextend you have the InnoDB Variables in the wrong section

Re: mysqld-max-nt 4.0.1-alpha shutdown problem

2002-07-15 Thread Egor Egorov
Roman, Monday, July 15, 2002, 8:07:07 AM, you wrote: RV> When mysqld-max-nt.exe is started with options RV> --console --standalone RV> and after issuing "mysqladmin -u root shutdown" RV> mysqld reports a shutdown, but does not exit. RV> mysqld-max don't have this problem. RV> OS Windows 2000.

Re: MySQLd-MAX Crash - Possible Bug v3.23.47?

2002-01-17 Thread Heikki Tuuri
Rich, it was a bug. If inserts to several tables containing an auto-inc column are wrapped inside one LOCK TABLES, InnoDB will assert in lock0lock.c, line 2843. Workaround: remove the LOCK TABLES if you can, or LOCK just one table at a time. I have fixed the bug to 3.23.48. You will get a patch