RE: Red Hat 8.0 compile problems with 4.0.10

2003-02-19 Thread Duncan Maitland
the recommended 192K still results in the same error. I'm not really sure what I'm supposed to be looking for - are there any further tests that I can run that would be of any use? Regards, Duncan Maitland. - Before posting, please check

Red Hat 8.0 compile problems with 4.0.10

2003-02-14 Thread Duncan Maitland
_db_doprnt_ + 189 0x80ab6de _Z19close_thread_tablesP3THDb + 290 0x8095113 handle_bootstrap + 779 0x823a6d5 pthread_start_thread + 177 0x827669a thread_start + 4 If anyone has any ideas, or even better, if anyone has a solution to this problem then please reply to this post. Many thanks, Duncan

Red Hat 8.0 problems installing from source

2003-01-26 Thread Duncan Maitland
I am installing MySQL 4.0.9 on a server running Red Hat 8.0 but am running into some showstoppers. I seem to have success compiling - no warnings are raised - but mysql_install_db will crash when installing the grant tables. Initially I thought it may have been the hardware configuration (I

FULLTEXT relevance and phrase searching

2002-06-02 Thread Duncan Maitland
(body) AGAINST ('phrase search') * (LENGTH(body) - LENGTH(REPLACE(LOWER(body), LOWER('phrase search'),''))) / LENGTH('phrase search') AS relevance FROM ... However, I'm not sure if this is the most accurate method. Any other thoughts would be greatly appreciated! Regards, Duncan Maitland [EMAIL

FULLTEXT indexing / ACID transactions

2001-12-29 Thread Duncan Maitland
(or is there a good online resource?) Many thanks, from Duncan Maitland [EMAIL PROTECTED] - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request

Multiple copies of messages

2001-12-19 Thread Duncan Maitland
thought I'd check to see if everyone else has been receiving multiple copies as well. If so, then I can eliminate other possible sources of the problem. Thanks, from Duncan Maitland [EMAIL PROTECTED] - Before posting, please check

RE: No Database Encryption

2001-12-12 Thread Duncan Maitland
It's only dangerous if a customer can trick your web frontend into displaying the output of SELECT * FROM USERS, for example. If the frontend only uses hardcoded queries, or quotes every user-supplied parameter, there's no problem. In fact, you need the password in plaintext to support