If you'd like I can send you the configure "script" I used to set up MySQL
for Berkeley and InnoDB.
--Walt
-Original Message-
From: Ken Kinder [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:26 PM
To: Weaver, Walt; [EMAIL PROTECTED]
Subject: Re: Forcing Tabl
ecember 28, 2001 12:26 PM
To: Weaver, Walt; [EMAIL PROTECTED]
Subject: Re: Forcing Table Types
I am using the RPM's, but it didn't give an error so I'm assuming it is
properly configured. The MySQL version is:
[ken@ken ken]$ mysql --version
mysql Ver 11.15 Distrib 3.23.44, for pc-lin
Hi!
On Dec 28, Ken Kinder wrote:
> This is getting really annoying. No matter what type of table I create, it
> ends up being MyISAM. I _must_ have at least transactions and foreign key
> support would be nice. Also, does anyone know how I can have transactions on
> create table statements?
T
al Message-
> From: Ken Kinder [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 28, 2001 1:09 PM
> To: [EMAIL PROTECTED]
> Subject: Forcing Table Types
>
>
> This is getting really annoying. No matter what type of table I create, it
> ends up being MyISAM. I _must_ have
inder [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 28, 2001 1:09 PM
To: [EMAIL PROTECTED]
Subject: Forcing Table Types
This is getting really annoying. No matter what type of table I create, it
ends up being MyISAM. I _must_ have at least transactions and foreign key
support would be nice. Also,
This is getting really annoying. No matter what type of table I create, it
ends up being MyISAM. I _must_ have at least transactions and foreign key
support would be nice. Also, does anyone know how I can have transactions on
create table statements?
Here the interaction with MySQL that is dri
