RE: JBoss queries aren't cached by MySQL

Hi again, The query cache finally works after I've reverted to mm.mysql-2.0.12-bin.jar. The problem was that the query cache somehow wouldn't work within transactions with mysql-connector-java-3.1.10-bin.jar. Anyone care to dig further? Here is one working combination: Jboss 3.2.2 with transact

RE: JBoss queries aren't cached by MySQL

he general log to be sure that MySQL receives unchanged queries and no session variables has been changed. "Al Caponi" <[EMAIL PROTECTED]> wrote: > Hi All, > I didn't see any follow-up on this thread. Hope I can get some hint :) > How to get the query cache to work

RE: JBoss queries aren't cached by MySQL

Hi again, It seems that the problem is solved with MySQL 4.1 (and later?). See a posting from the Jboss forum: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830750#3830750 Cheers, Al -Original Message- From: Al Caponi [mailto:[EMAIL PROTECTED] Sent: Wednesday, Oc

RE: JBoss queries aren't cached by MySQL

Hi All, I didn't see any follow-up on this thread. Hope I can get some hint :) How to get the query cache to work with Jboss? I've got my app running on the following JBoss 3.2.2. (Unable to upgrade right now) MySQL 4.0.20d mysql-connector-java-3.1.10-bin.jar I have switched on the query_cache

RE: Key Buffer Size

i did: http://www.mysql.com/doc/en/Server_system_variables.html -Original Message- From: Terence [mailto:[EMAIL PROTECTED] Sent: Friday, March 19, 2004 3:11 PM To: [EMAIL PROTECTED] Subject: Key Buffer Size Hi, Can somebody tell me whether this is good or bad: Our mysql server has key_b

Win98 - Work-around to sudden lost connection to database

Hi all, There is a limitation on Win98 when a client app using mm.mysql driver doing extensive queries to MySQL 3.23.x frequently encounters a connection lost error. Error msg is something like: 'java.lang.Exception: Cannot connect to MySQL server on localhost:3306. Is there a MySQL server runnin

RE: MySQL 3.23.39 shuts down by itself on Win2K

Nope. That is not the case here because the connections to the database are autoReconnect=true. > -Original Message- > From: Terrance Win [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 02, 2003 7:42 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Re: MySQL 3.23.39 shuts d

MySQL 3.23.39 shuts down by itself on Win2K

Hi all, (BI've got a java application running with MySQL 3.23.39 on a Win2K server. (BNo other application uses this MySQL server. (BAnd yesterday it just shut down without any reason. This is the second time. (BThe first time was a few months back and I didn't pay attention to it. (BDoes any

RE: Inserting strings containing spaces only fails?

It's in the doco: http://www.mysql.com/doc/C/H/CHAR.html Values in VARCHAR columns are variable-length strings. You can declare a VARCHAR column to be any length between 1 and 255, just as for CHAR columns. However, in contrast to CHAR, VARCHAR values are stored using only as many characters as

RE: NULL timestamps not possible?

> Of course, the page lies somewhat: it says that if you omit the column in > an insert, it should get set to now(), but the following example shows it > doesn't - notice that "u" is omitted in the insert, but gets set to 0 > instead of now(). > > >>create table foo (t timestamp, u timestamp);

RE: encrypt password

http://www.mysql.com/doc/M/i/Miscellaneous_functions.html Using the PASSWORD function is an irreversible process. Check the above link. A work around is you always deal with the encrypted password on the server side. E.g. When the user will login you encrypt the submitted password and do a SELEC

RE: change column to not null in MySQL

Check out the MySQL website for altering table structure: http://www.mysql.com/doc/A/L/ALTER_TABLE.html You could use MODIFY to change the columns definition in your tables. Note that specifying NOT NULL on a column will not affect existing rows where that field already contains a NULL value. R

RE: FULLTEXT error?

Hi Doug, What's the MySQL version you're running? Your SQL query worked fine on my PC. MySQL 3.23.47 Win98SE Last time I had some problem (that was 3.23.32 I think) when mixing VARCHAR and TEXT types in the FULLTEXT index. After upgrading to MySQL 3.23.47, I did not encounter anymore problem lik

RE: Date Manipulation

AFAIK, you'll have to do the conversion before inserting the date into the database because MySQL does not support the MMDD format. Regards, Al > -Original Message- > From: S Aravind [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 26, 2002 5:12 PM > To: [EMAIL PROTECTED] > Subje

RE: Limitation of Full-Text indexing in MyISAM table?

> > > > > > > On Dec 10, Al Caponi wrote: > > > > > > > > > > But I keep getting the following error when I try to delete > > some row: > > > > > > > > > > java.sql.SQLException: General error: Incorrect key f

RE: Limitation of Full-Text indexing in MyISAM table?

Hi, > > > > > > Hi! > > > > > > On Dec 10, Al Caponi wrote: > > > > > > > > But I keep getting the following error when I try to delete > some row: > > > > > > > > java.sql.SQLException: General error: Incorre

RE: Limitation of Full-Text indexing in MyISAM table?

Hi Sergei! Thanks for the reply! That was fast :) > -Original Message- > From: Sergei Golubchik [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 10, 2001 10:48 PM > To: Al Caponi > Cc: MySQL Mailing List > Subject: Re: Limitation of Full-Text indexing in MyISAM table

Limitation of Full-Text indexing in MyISAM table?

Hi all, Is there any limitation in creating full-text indexes on MyISAM tables? Currently, I have a table like this: CREATE TABLE IF NOT EXISTS mytable ( UId BIGINT(20) NOT NULL AUTO_INCREMENT, Title VARCHAR(255) NOT NULL, Field1 TEXT, Field2 TEXT, Field3 VA