TECTED]
> Sent: Monday, September 08, 2003 8:07 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Questions abou innodb
>
>
> InnoDB of course does not support
> > FULLTEXT indexes, and so forth.
>
> Which is a pain, because i want the foreign key relationships
> b
> start transaction
> do query
> if error
> rollback
> else
> commit
>
>
> --
Heh thats what i meant ;)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
At 13:06 +1000 9/9/03, <[EMAIL PROTECTED]> wrote:
InnoDB of course does not support
FULLTEXT indexes, and so forth.
Which is a pain, because i want the foreign key relationships but fulltext
indexing at the same time :\
As for transactions , is it simply by doing this?
start transaction
do query
InnoDB of course does not support
> FULLTEXT indexes, and so forth.
Which is a pain, because i want the foreign key relationships but fulltext
indexing at the same time :\
As for transactions , is it simply by doing this?
start transaction
do query
commit
if error
rollback
??
--
MySQL Gen
> 1) can you join a MyISAM table to an innodb table in a select?
Absolutely.
> 2) Under 'Restrictions...' in the manual, it says:
> When you restart the MySQL server, InnoDB may reuse an old
> value for an
> AUTO_INCREMENT column.
> Under what circumstances does this occur?
If you perform an I
Hi i have just started to use them aswell to do proper relationships
between tables to add data restrictions on deleting records.
>
> 1) can you join a MyISAM table to an innodb table in a select?
This seems to work.
>
> 2) Under 'Restrictions...' in the manual, it says:
> When you restart the M
We're considering switching to InnoDB tables for a couple of tables in
our database where we need transactions. We're complete newbies with
reference to innodb, although we are seasoned veterans with regards to
MySQL/MyISAM and general concepts.
We have come up with a couple questions that we have
