James Powell wrote:
> On Thu, Mar 29, 2001 at 09:59:35AM +0100, Dominic Mitchell wrote:
> > On Thu, Mar 29, 2001 at 08:56:36AM +0100, James Powell wrote:
> > > Course, mysql does support transactions now... I believe with two
> > > different types of table for some reason.
> >
> > It's because the underlying table type is implemented using Berkeley
> > DB3, which does support transactions.  And that has several modes of
> > operation, hash, btree and recno.
> >
> > I haven't looked into it, but I would imagine that it makes transactions
> > across different tables kind of tricky.  In fact, I'd class it as a bit
> > of a hack.  But don't take my opinion for it, because this is all based
> > on 2nd hand evidence.
> >
> > -Dom
> But as well as Berkeley there's innobase and gemini (not in yet?)
> table types that support transactions.
> http://www.mysql.com/documentation/mysql/bychapter/manual_Table_types.html
> I can't say I've used any of them or would trust any of them...

I've tested innobase and it appears to be fine.  It very Oracle like in
the way it works (it needs loasd of resources to run quickly).  MyISAM
table handlers for speed and Innobase table handlers for transaction
based tables (also with row locking) and you should be away.  (The
Innobase code is apparently not new, and has been taken from another
project and bolted on, which sounds bad but actually appears to work
quite well).


> And MySQL has got full-text indexing now - didn't notice that one
> http://www.mysql.com/news/article-54.html
> "MySQL 3.23 now has full-text indexing and searching capabilities. This
> allows you to search your vast databases of
> textual information, with queries returning search string
> occurrence/relevance."
> Incidentally, saw your ssh letter in the new LJ...
> jp

Reply via email to