Thanks Aaron. It's using MySQL MaxDB 7.5.0. I've checked out HEAD and
got things to configure --with-maxdb=/opt/sdb and build. It runs
dbmail-util -v -a -c -y, although aside from db_query and db_do_cleanup
it's still basically stub functions. It does fail on quota check, but
that's because MaxDB doesn't like the query. Made an SQL file to load up
the tables too, although I need to add a bunch of indexes and triple
check everything. I'll fill in some more functions this week.
This is the error anway:
Jan 30 16:42:08 testbox dbmail/maintenance[19169]: dbmaxdb.c,db_query:
Execution failed POS(1) Outer join not allowed in this context.
Statement was SELECT usr.user_idnr, sum(pm.messagesize),
usr.curmail_size FROM dbmail_users usr LEFT JOIN dbmail_mailboxes mbx ON
mbx.owner_idnr = usr.user_idnr LEFT JOIN dbmail_messages msg ON
msg.mailbox_idnr = mbx.mailbox_idnr LEFT JOIN dbmail_physmessage pm ON
pm.id = msg.physmessage_id AND msg.status < '2' GROUP BY usr.user_idnr,
usr.curmail_size HAVING ((SUM(pm.messagesize) <> usr.curmail_size) OR
(NOT (SUM(pm.messagesize) IS NOT NULL) AND usr.curmail_size <> 0))
Jan 30 16:42:08 testbox dbmail/maintenance[19169]:
db.c,db_calculate_quotum_all: error findng quotum used
Richard.
Aaron Stone wrote:
The backend database functions are almost exactly the same, so you're find
coding basically for both, but you are correct that the new backend would
probably (well, definitely) only be added to the 2.1 development line.
