Re: LOAD_FILE over SMB filesystems

On Wed, 2002-01-23 at 07:42, Egor Egorov wrote: > Panos, > > Tuesday, January 22, 2002, 5:42:20 PM, you wrote: > > PM> I have some problems loading files into blobs when the file > PM> resides on a network filesystem e.g. SAMBA. I use mysqld > PM> 3.23.43-nt. > > PM> e.g. > > PM> UPDATE Readi

Re: mysql magically restarts of its own accord

> Rich, > >>06 13:38:46 mysqld restarted >>InnoDB: Database was not shut down normally. >>InnoDB: Starting recovery from log files... >>InnoDB: Starting log scan based on checkpoint at >>InnoDB: log sequence number 5 778892274 >>InnoDB: Doing recovery: scanned up to log sequence number 5 7789

Re: Cannot add blob data to innodb table

> > how do you communicate the binary strings to MySQL? From the manual I > found: > > " > If you want to insert binary data into a BLOB column, the following > characters must be represented by escape sequences: > > NUL > ASCII 0. You should represent this by `\0' (a backslash and an ASCII > `0'

Re: Cannot add blob data to innodb table

Hi Heikki, Comments inserted in text below: > Steve, > >>Date: Mon, 12 Nov 2001 08:52:54 >>To: [EMAIL PROTECTED] >>From: Heikki Tuuri <[EMAIL PROTECTED]> >>Subject: Re: Cannot add blob data to innodb table >> >>Stephen, >> >>>Hi, >>> >>>I have an Access97 table containing binary fields (gifs) th

Re: Innodb file sizes

> In the last episode (Nov 02), Stephen Lee said: >> I have the following settings in /etc/my.cnf: >> >> default-table-type=innodb >> innodb_data_file_path = ibdata1:1000M >> set-variable = innodb_log_file_size=5M >> >> The resulting files: >> -

Innodb file sizes

I have the following settings in /etc/my.cnf: default-table-type=innodb innodb_data_file_path = ibdata1:1000M innodb_data_home_dir = /var/lib/mysql/ innodb_log_group_home_dir = /var/lib/mysql/ innodb_log_arch_dir = /var/lib/mysql/ set-variable = innodb_mirrored_log_groups=1 set-variable = innodb_

Re: MySQL-Max database recovery crashed - Fixed!

> Stephen, > > At 01:37 PM 11/2/01 -0800, you wrote: >>> Stephen, >>> >>> At 12:38 PM 11/2/01 -0800, you wrote: Heikki, Removal of the log= option and even the log-bin statement did not help. I used the latest (2.23.44) RPMs from one of the mysql.com mirrors. I don't think it'

Re: MySQL-Max database recovery crashed

> Stephen, > > At 12:38 PM 11/2/01 -0800, you wrote: >>Heikki, >> >>Removal of the log= option and even the log-bin statement did not help. >>I used the latest (2.23.44) RPMs from one of the mysql.com mirrors. I >>don't think it's a download issue because the problem originally >>occured with the

Re: MySQL-Max database recovery crashed

Heikki, Removal of the log= option and even the log-bin statement did not help. I used the latest (2.23.44) RPMs from one of the mysql.com mirrors. I don't think it's a download issue because the problem originally occured with the 2.23.43 distribution. The crash occurs within seconds of startin

Re: MySQL-Max database recovery crashed

> Stephen, > > I resolved the stack dump based on the 3.23.43 symbols file. I do not > understand what mysqld is trying to do here. Are you sure the stack > dump is from 3.23.43? > > 0x807b90f init_signals__Fv + 71 > 0x8253c7a __tfx + 26 > 0x80cf21a index_prev__11ha_innobasePc + 74 > 0x8078693 mys

MySQL-Max database recovery crashed

I converted my myISAM tables to Innodb format and everything went fine. When I restarted MySQL-Max (2.23.43) I noticed that my query log file was not being accessed anymore so I included "log=/var/lib/mysql/server1.log" to /etc/my.cnf. Running MySQL-Max this time though caused a continuous restart