Hi,
ISAM and MyISAM are venerable but it looks as if even MySQL AB
themselves are relying heavily on InnoDB. The fact that we can have
foregin keys now with InnoDB is
a massive benefit (MyISAM won't get this until it's implemented for all
table types, which is slated for MySQL 5.0).
There is one advantage that MyISAM tables have, and that's their
FULLTEXT index capabilities.
Regards,
Chris
Ilja Booij wrote:
Hi,
sorry, no transactions. I'd like for dbmail to use them, but currently
there is MySQL ISAM table support. These ISAM tables do not support
Transactions.
Anyone have any thoughts on why we should keep support for ISAM tables
in dbmail? Dropping this and going of innoDB only on MySQL seems like
a good idea to me.
cheers,
Ilja
On Thursday, Aug 28, 2003, at 12:38 Europe/Amsterdam, Chris Nolan wrote:
All hail Ilja!
I have one question though - any chance of using transactions?
Regards,
Chris
Ilja Booij wrote:
Hi all,
finally, the new database code is in CVS. It is totally untested (it
compiles), and will be tested when I'm finished with an urgent
project that has started this week. The new code can be found in the
dbmail_2_0 CVS branch (you can take a look
at the code and diffs without downloading by going to
http://cvs.dbmail.org).
* database code
The following changes have been made:
dbmysql.c and dbpgsql.c now only consist of functions which
implement API specific functionality. db.c (new file) implements all
database functions which used to be implemented by db??sql.c .
The same goes for dbsearch??sql.c and dbmsgbuf??sql.c, which are now
implemented by dbsearch.c and dbmsgbuf.c
* Authentication
The authentication code from dbauth??sql.c has been moved to a new
auth/ directory. There are two C-files there. authsql.c which
implements "classic" SQL authentication. authldap.c implements LDAP
authentication as implemented by Aaron Stone ([EMAIL PROTECTED]).
I've added a configure switch --with-auth-ldap which will compile
dbmail with this LDAP code.
* Query improvement
In db.c some queries have been made "better" by putting the
intelligence into the SQL query instead of the C-code
(db_icheck_messages() is an example of this).
* InnoDB
Paul Stevens posted some better MySQL innoDB tables definitions to
the dbmail@dbmail.org list, which have now taken the place of the
old innoDB definitions.
* Warnings
The configure script now adds -W -Wall to the gcc flags. There are
quite a lot of warnings currently (most have to do with
unsigned<->signed conflicts), which have to be taken care of. I'd
like the package to compile cleanly.
* Doxygen
To help developers to get a good view of the code, I've started
documenting all functions with doxygen (www.doxygen.org) tags. For
those of you who don't know doxygen, think of it as an improved
JavaDoc, which makes hyperlinked HTML pages for all source files.
* Website
I hope to be able to update www.dbmail.org next week.
* WARNING
Again, this is alpha code. Please try it, look at the code, send
your comments, etc. Don't use this in a production environment yet.
cheers,
Ilja Booij
--
IC&S
Koningsweg 4
3582 GE UTRECHT
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
