Mailing List Archive

Using MySQL 4.0 already, but I'm pretty there are some people still using
3.x.

Maybe until 2.1 or (2.0.x) there could be two sourcefiles or a patch you
could apply which introduced the 'not-so-efficient' code back again until
people are given a chance to upgrade.

It may not be worth the effort if too complicated, or if noone shouts out
saying they can't upgrade, etc.

/Mark

> -----Original Message-----
> From: dbmail-dev-bounces@dbmail.org
> [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> Sent: Monday, 15 March 2004 1:01 a.m.
> To: dbmail-dev@dbmail.org
> Subject: [Dbmail-dev] Bunch of fixes and improvements, but
> with a catch
>
>
> Hey,
>
> So I was reading through the sorting code, and realized that
> the copy of each
> message from the temporary delivery user to the destination
> user was much more
> expensive than I thought. I have rewritten db_copymsg() to
> use just 3 queries,
> where it used to be something like 10 queries!
>
> The catch is that MySQL 4.0.14 or higher is required because
> prior to 4.0.14,
> an INSERT INTO table1 ... SELECT FROM table2, where table1 ==
> table2, was not
> allowed. All versions of PostgreSQL support this SQL92
> compliant query, though.
>
> IMHO, this is a really important feature and it is well worth
> excluding those
> earlier MySQL versions to get support for it; Ilja, is that
> OK with you?
>
> Aaron
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>

I'm fairly certain that we're already using features of 4.0... although I
agree that if we're not yet requiring 4.0 in the first place, then it's
somewhat silly to discuss which revision of 4.0 should be the minimum.

It wouldn't be hard to switch back to the previous pair of queries, but it
sure would be nice to use the single query!

Aaron


"Mark Mackay - Orcon" <mark@orcon.net.nz> said:

> Using MySQL 4.0 already, but I'm pretty there are some people still using
> 3.x.
>
> Maybe until 2.1 or (2.0.x) there could be two sourcefiles or a patch you
> could apply which introduced the 'not-so-efficient' code back again until
> people are given a chance to upgrade.
>
> It may not be worth the effort if too complicated, or if noone shouts out
> saying they can't upgrade, etc.
>
> /Mark
>
> > -----Original Message-----
> > From: dbmail-dev-bounces@dbmail.org
> > [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> > Sent: Monday, 15 March 2004 1:01 a.m.
> > To: dbmail-dev@dbmail.org
> > Subject: [Dbmail-dev] Bunch of fixes and improvements, but
> > with a catch
> >
> >
> > Hey,
> >
> > So I was reading through the sorting code, and realized that
> > the copy of each
> > message from the temporary delivery user to the destination
> > user was much more
> > expensive than I thought. I have rewritten db_copymsg() to
> > use just 3 queries,
> > where it used to be something like 10 queries!
> >
> > The catch is that MySQL 4.0.14 or higher is required because
> > prior to 4.0.14,
> > an INSERT INTO table1 ... SELECT FROM table2, where table1 ==
> > table2, was not
> > allowed. All versions of PostgreSQL support this SQL92
> > compliant query, though.
> >
> > IMHO, this is a really important feature and it is well worth
> > excluding those
> > earlier MySQL versions to get support for it; Ilja, is that
> > OK with you?
> >
> > Aaron
> > _______________________________________________
> > 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
>



--

There are other reasons to upgrade to 4.0 aside from the new features.
On 3.23 w/ the latest (as of yesterday) CVS I was getting errors like these:

/var/log/maillog.1-Mar 13 15:01:32 sls-cd7p8 dbmail/imap4d[20655]:
PerformChildTask(): incoming connection from [127.0.0.1]
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
COMMAND: [1 capability]
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
COMMAND: [2 authenticate login]
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]: IMAPD
[PID 20655]: user (id 1, name blake) login accepted @ 2004-03-13 15:01:33^M
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
COMMAND: [3 namespace]
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
COMMAND: [4 lsub "" "*"]
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
dbmysql.c,db_query: query [.SELECT mbx.name, mbx.mailbox_idnr,
mbx.owner_idnr FROM mailboxes mbx LEFT JOIN acl ON acl.mailbox_id =
mbx.mailbox_idnr JOIN subscription sub ON sub.user_id = '1' AND
sub.mailbox_id = mbx.mailbox_idnr WHERE mbx.owner_idnr = '1' OR
(acl.user_id = '1' AND acl.lookup_flag = '1') GROUP BY mbx.name,
mbx.mailbox_idnr, mbx.owner_idnr] failed
/var/log/maillog.1:Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
dbmysql.c,db_query: mysql_real_query failed: You have an error in your
SQL syntax near 'ON sub.user_id = '1' AND sub.mailbox_id =
mbx.mailbox_idnr WHERE mbx.owner_idnr ' at line 1
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
db.c,db_list_mailboxes_by_regex: error during mailbox query
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
db.c,db_findmailbox_by_regex: error listing mailboxes
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
IMAPClientHandler(): Closing connection for client from IP [127.0.0.1]
/var/log/maillog.1-Mar 13 15:01:33 sls-cd7p8 dbmail/imap4d[20655]:
PerformChildTask(): maximum number of connections reached, stopping now

After upgrading to 4.0.18, these problems disappeared. I think this is
because older mysql doesn't like mixing left and inner joins.

Cheers,
Blake

Aaron Stone wrote:

>Hey,
>
>So I was reading through the sorting code, and realized that the copy of each
>message from the temporary delivery user to the destination user was much more
>expensive than I thought. I have rewritten db_copymsg() to use just 3 queries,
>where it used to be something like 10 queries!
>
>The catch is that MySQL 4.0.14 or higher is required because prior to 4.0.14,
>an INSERT INTO table1 ... SELECT FROM table2, where table1 == table2, was not
>allowed. All versions of PostgreSQL support this SQL92 compliant query, though.
>
>IMHO, this is a really important feature and it is well worth excluding those
>earlier MySQL versions to get support for it; Ilja, is that OK with you?
>
>Aaron
>_______________________________________________
>Dbmail-dev mailing list
>Dbmail-dev@dbmail.org
>http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>
>

Sounds like it would be good to have in place as soon as possible, so those
of us using new versions can get the optimizations.

Maybe a compile-time option or something for 1-2 months?

Or perhaps a runtime check -- call the select version() function and make
sure is high enough, etc.

/Mark

> -----Original Message-----
> From: dbmail-dev-bounces@dbmail.org
> [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> Sent: Monday, 15 March 2004 7:46 a.m.
> To: dbmail-dev@dbmail.org
> Subject: RE: [Dbmail-dev] Bunch of fixes and improvements,
> but with a catch
>
> I'm fairly certain that we're already using features of
> 4.0... although I
> agree that if we're not yet requiring 4.0 in the first place,
> then it's
> somewhat silly to discuss which revision of 4.0 should be the minimum.
>
> It wouldn't be hard to switch back to the previous pair of
> queries, but it
> sure would be nice to use the single query!
>
> Aaron
>
>
> "Mark Mackay - Orcon" <mark@orcon.net.nz> said:
>
> > Using MySQL 4.0 already, but I'm pretty there are some
> people still using
> > 3.x.
> >
> > Maybe until 2.1 or (2.0.x) there could be two sourcefiles
> or a patch you
> > could apply which introduced the 'not-so-efficient' code
> back again until
> > people are given a chance to upgrade.
> >
> > It may not be worth the effort if too complicated, or if
> noone shouts out
> > saying they can't upgrade, etc.
> >
> > /Mark
> >
> > > -----Original Message-----
> > > From: dbmail-dev-bounces@dbmail.org
> > > [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> > > Sent: Monday, 15 March 2004 1:01 a.m.
> > > To: dbmail-dev@dbmail.org
> > > Subject: [Dbmail-dev] Bunch of fixes and improvements, but
> > > with a catch
> > >
> > >
> > > Hey,
> > >
> > > So I was reading through the sorting code, and realized that
> > > the copy of each
> > > message from the temporary delivery user to the destination
> > > user was much more
> > > expensive than I thought. I have rewritten db_copymsg() to
> > > use just 3 queries,
> > > where it used to be something like 10 queries!
> > >
> > > The catch is that MySQL 4.0.14 or higher is required because
> > > prior to 4.0.14,
> > > an INSERT INTO table1 ... SELECT FROM table2, where table1 ==
> > > table2, was not
> > > allowed. All versions of PostgreSQL support this SQL92
> > > compliant query, though.
> > >
> > > IMHO, this is a really important feature and it is well worth
> > > excluding those
> > > earlier MySQL versions to get support for it; Ilja, is that
> > > OK with you?
> > >
> > > Aaron
> > > _______________________________________________
> > > 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
>

According to Blake Mitchell's post a few hours ago, we're already using MySQL
4.0 features in some of the JOIN syntax. Really by "features" I mean "support
for long standing, published SQL92 specifications" -- most or all of which are
supported by PostgreSQL (and I know that PostgreSQL people hate having their
queries dumbed down to support MySQL; not that I always agree with them,
because MySQL is so frickin' fast, but it's a valid argument).

My vote is towards dropping MySQL 3.x entirely and picking some reasonable
point release in the 4.0 series where there's sufficient support for features
that we really want to use. I don't expect this to be an entirely democratic
process, though, so I'm just shoving my $0.02 out there until Ilja and Co.
check their email in a couple of hours and give us the verdict ;-)

Aaron


""Mark Mackay - Orcon"" <mark@orcon.net.nz> said:

> Sounds like it would be good to have in place as soon as possible, so those
> of us using new versions can get the optimizations.
>
> Maybe a compile-time option or something for 1-2 months?
>
> Or perhaps a runtime check -- call the select version() function and make
> sure is high enough, etc.
>
> /Mark
>
> > -----Original Message-----
> > From: dbmail-dev-bounces@dbmail.org
> > [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> > Sent: Monday, 15 March 2004 7:46 a.m.
> > To: dbmail-dev@dbmail.org
> > Subject: RE: [Dbmail-dev] Bunch of fixes and improvements,
> > but with a catch
> >
> > I'm fairly certain that we're already using features of
> > 4.0... although I
> > agree that if we're not yet requiring 4.0 in the first place,
> > then it's
> > somewhat silly to discuss which revision of 4.0 should be the minimum.
> >
> > It wouldn't be hard to switch back to the previous pair of
> > queries, but it
> > sure would be nice to use the single query!
> >
> > Aaron
> >
> >
> > "Mark Mackay - Orcon" <mark@orcon.net.nz> said:
> >
> > > Using MySQL 4.0 already, but I'm pretty there are some
> > people still using
> > > 3.x.
> > >
> > > Maybe until 2.1 or (2.0.x) there could be two sourcefiles
> > or a patch you
> > > could apply which introduced the 'not-so-efficient' code
> > back again until
> > > people are given a chance to upgrade.
> > >
> > > It may not be worth the effort if too complicated, or if
> > noone shouts out
> > > saying they can't upgrade, etc.
> > >
> > > /Mark
> > >
> > > > -----Original Message-----
> > > > From: dbmail-dev-bounces@dbmail.org
> > > > [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> > > > Sent: Monday, 15 March 2004 1:01 a.m.
> > > > To: dbmail-dev@dbmail.org
> > > > Subject: [Dbmail-dev] Bunch of fixes and improvements, but
> > > > with a catch
> > > >
> > > >
> > > > Hey,
> > > >
> > > > So I was reading through the sorting code, and realized that
> > > > the copy of each
> > > > message from the temporary delivery user to the destination
> > > > user was much more
> > > > expensive than I thought. I have rewritten db_copymsg() to
> > > > use just 3 queries,
> > > > where it used to be something like 10 queries!
> > > >
> > > > The catch is that MySQL 4.0.14 or higher is required because
> > > > prior to 4.0.14,
> > > > an INSERT INTO table1 ... SELECT FROM table2, where table1 ==
> > > > table2, was not
> > > > allowed. All versions of PostgreSQL support this SQL92
> > > > compliant query, though.
> > > >
> > > > IMHO, this is a really important feature and it is well worth
> > > > excluding those
> > > > earlier MySQL versions to get support for it; Ilja, is that
> > > > OK with you?
> > > >
> > > > Aaron
> > > > _______________________________________________
> > > > 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
> >
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>



--

Fine by me. As long as we don't require anything ahead of the current Debian
'testing' MySQL version ;)

/Mark

That's a really good point! So we should all add this url (newlines added for
clarity) to our collective memories:

http://packages.debian.org/cgi-bin/search_packages.pl?
keywords=mysql-server
&searchon=names
&subword=1
&version=all
&release=all

Aaron


""Mark Mackay - Orcon"" <mark@orcon.net.nz> said:

> Fine by me. As long as we don't require anything ahead of the current Debian
> 'testing' MySQL version ;)
>
> /Mark
>
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev
>

--

I say dump the older versions of mysql as well.

SB

Aaron Stone <aaron@serendipity.palo-alto.ca.us> wrote:
According to Blake Mitchell's post a few hours ago, we're already using MySQL
4.0 features in some of the JOIN syntax. Really by "features" I mean "support
for long standing, published SQL92 specifications" -- most or all of which are
supported by PostgreSQL (and I know that PostgreSQL people hate having their
queries dumbed down to support MySQL; not that I always agree with them,
because MySQL is so frickin' fast, but it's a valid argument).

My vote is towards dropping MySQL 3.x entirely and picking some reasonable
point release in the 4.0 series where there's sufficient support for features
that we really want to use. I don't expect this to be an entirely democratic
process, though, so I'm just shoving my $0.02 out there until Ilja and Co.
check their email in a couple of hours and give us the verdict ;-)

Aaron


""Mark Mackay - Orcon"" said:

> Sounds like it would be good to have in place as soon as possible, so those
> of us using new versions can get the optimizations.
>
> Maybe a compile-time option or something for 1-2 months?
>
> Or perhaps a runtime check -- call the select version() function and make
> sure is high enough, etc.
>
> /Mark
>
> > -----Original Message-----
> > From: dbmail-dev-bounces@dbmail.org
> > [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> > Sent: Monday, 15 March 2004 7:46 a.m.
> > To: dbmail-dev@dbmail.org
> > Subject: RE: [Dbmail-dev] Bunch of fixes and improvements,
> > but with a catch
> >
> > I'm fairly certain that we're already using features of
> > 4.0... although I
> > agree that if we're not yet requiring 4.0 in the first place,
> > then it's
> > somewhat silly to discuss which revision of 4.0 should be the minimum.
> >
> > It wouldn't be hard to switch back to the previous pair of
> > queries, but it
> > sure would be nice to use the single query!
> >
> > Aaron
> >
> >
> > "Mark Mackay - Orcon" said:
> >
> > > Using MySQL 4.0 already, but I'm pretty there are some
> > people still using
> > > 3.x.
> > >
> > > Maybe until 2.1 or (2.0.x) there could be two sourcefiles
> > or a patch you
> > > could apply which introduced the 'not-so-efficient' code
> > back again until
> > > people are given a chance to upgrade.
> > >
> > > It may not be worth the effort if too complicated, or if
> > noone shouts out
> > > saying they can't upgrade, etc.
> > >
> > > /Mark
> > >
> > > > -----Original Message-----
> > > > From: dbmail-dev-bounces@dbmail.org
> > > > [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> > > > Sent: Monday, 15 March 2004 1:01 a.m.
> > > > To: dbmail-dev@dbmail.org
> > > > Subject: [Dbmail-dev] Bunch of fixes and improvements, but
> > > > with a catch
> > > >
> > > >
> > > > Hey,
> > > >
> > > > So I was reading through the sorting code, and realized that
> > > > the copy of each
> > > > message from the temporary delivery user to the destination
> > > > user was much more
> > > > expensive than I thought. I have rewritten db_copymsg() to
> > > > use just 3 queries,
> > > > where it used to be something like 10 queries!
> > > >
> > > > The catch is that MySQL 4.0.14 or higher is required because
> > > > prior to 4.0.14,
> > > > an INSERT INTO table1 ... SELECT FROM table2, where table1 ==
> > > > table2, was not
> > > > allowed. All versions of PostgreSQL support this SQL92
> > > > compliant query, though.
> > > >
> > > > IMHO, this is a really important feature and it is well worth
> > > > excluding those
> > > > earlier MySQL versions to get support for it; Ilja, is that
> > > > OK with you?
> > > >
> > > > Aaron
> > > > _______________________________________________
> > > > 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
> >
>
> _______________________________________________
> 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
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam

Hi,

MySQL >= 4.0.14 does not seem like very bad thing to require.

Of course, we're using debian stable here, which still has 3.23.x as its
MySQL version.. But that shouldn't be too much of a problem :). We could
just install from source or the binary tarballs at mysql.com

We should go for the new statements! :D

Ilja

Aaron Stone wrote:

> Hey,
>
> So I was reading through the sorting code, and realized that the copy of each
> message from the temporary delivery user to the destination user was much more
> expensive than I thought. I have rewritten db_copymsg() to use just 3 queries,
> where it used to be something like 10 queries!
>
> The catch is that MySQL 4.0.14 or higher is required because prior to 4.0.14,
> an INSERT INTO table1 ... SELECT FROM table2, where table1 == table2, was not
> allowed. All versions of PostgreSQL support this SQL92 compliant query, though.
>
> IMHO, this is a really important feature and it is well worth excluding those
> earlier MySQL versions to get support for it; Ilja, is that OK with you?
>
> Aaron
> _______________________________________________
> Dbmail-dev mailing list
> Dbmail-dev@dbmail.org
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev

Ilja Booij wrote:
> Hi,
>
> MySQL >= 4.0.14 does not seem like very bad thing to require.
>
> Of course, we're using debian stable here, which still has 3.23.x as its
> MySQL version.. But that shouldn't be too much of a problem :). We could
> just install from source or the binary tarballs at mysql.com

Or add the following line to at the top of /etc/apt/sources.list
deb http://packages.dotdeb.org

This source supplies backports of MySQL and PHP to Woody

Magnus

>
> We should go for the new statements! :D
>
> Ilja
>
> Aaron Stone wrote:
>
>> Hey,
>>
>> So I was reading through the sorting code, and realized that the copy
>> of each
>> message from the temporary delivery user to the destination user was
>> much more
>> expensive than I thought. I have rewritten db_copymsg() to use just 3
>> queries,
>> where it used to be something like 10 queries!
>>
>> The catch is that MySQL 4.0.14 or higher is required because prior to
>> 4.0.14,
>> an INSERT INTO table1 ... SELECT FROM table2, where table1 == table2,
>> was not
>> allowed. All versions of PostgreSQL support this SQL92 compliant
>> query, though.
>>
>> IMHO, this is a really important feature and it is well worth
>> excluding those
>> earlier MySQL versions to get support for it; Ilja, is that OK with you?
>>
>> Aaron
>> _______________________________________________
>> 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

> Or add the following line to at the top of /etc/apt/sources.list
> deb http://packages.dotdeb.org

Way cool! Thanks for the info.
Much easier than my way :)

/Mark

On Tue, Mar 16, 2004 at 07:09:06AM +1300, Mark Mackay - Orcon wrote:
> > Or add the following line to at the top of /etc/apt/sources.list
> > deb http://packages.dotdeb.org
>
> Way cool! Thanks for the info.
> Much easier than my way :)

backports.org also has mysql packages, in addition to a ton of other
packages backported to woody.

xn

Since 2.0 will be a major release, now is the perfect time to lay down what versions of other software is required. I think any minimum requirements cited for 2.0 should be supported until the next major release cycle, presumably 2.2. If we go with supporting mysql 3.x in 2.0 now, then this problem will resurface time and time again.

Also, given that 4.0 has been the main production release since last March, I don't think anybody can complain. If they really do want to keep using mysql 3.x, they can always use the last 1.x release of dbmail.

On Mon, 15 Mar 2004 00:53:41 -0000
"Aaron Stone" <aaron@serendipity.palo-alto.ca.us> wrote:

> According to Blake Mitchell's post a few hours ago, we're already using MySQL
> 4.0 features in some of the JOIN syntax. Really by "features" I mean "support
> for long standing, published SQL92 specifications" -- most or all of which are
> supported by PostgreSQL (and I know that PostgreSQL people hate having their
> queries dumbed down to support MySQL; not that I always agree with them,
> because MySQL is so frickin' fast, but it's a valid argument).
>
> My vote is towards dropping MySQL 3.x entirely and picking some reasonable
> point release in the 4.0 series where there's sufficient support for features
> that we really want to use. I don't expect this to be an entirely democratic
> process, though, so I'm just shoving my $0.02 out there until Ilja and Co.
> check their email in a couple of hours and give us the verdict ;-)
>
> Aaron
>
>
> ""Mark Mackay - Orcon"" <mark@orcon.net.nz> said:
>
> > Sounds like it would be good to have in place as soon as possible, so those
> > of us using new versions can get the optimizations.
> >
> > Maybe a compile-time option or something for 1-2 months?
> >
> > Or perhaps a runtime check -- call the select version() function and make
> > sure is high enough, etc.
> >
> > /Mark
> >
> > > -----Original Message-----
> > > From: dbmail-dev-bounces@dbmail.org
> > > [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> > > Sent: Monday, 15 March 2004 7:46 a.m.
> > > To: dbmail-dev@dbmail.org
> > > Subject: RE: [Dbmail-dev] Bunch of fixes and improvements,
> > > but with a catch
> > >
> > > I'm fairly certain that we're already using features of
> > > 4.0... although I
> > > agree that if we're not yet requiring 4.0 in the first place,
> > > then it's
> > > somewhat silly to discuss which revision of 4.0 should be the minimum.
> > >
> > > It wouldn't be hard to switch back to the previous pair of
> > > queries, but it
> > > sure would be nice to use the single query!
> > >
> > > Aaron
> > >
> > >
> > > "Mark Mackay - Orcon" <mark@orcon.net.nz> said:
> > >
> > > > Using MySQL 4.0 already, but I'm pretty there are some
> > > people still using
> > > > 3.x.
> > > >
> > > > Maybe until 2.1 or (2.0.x) there could be two sourcefiles
> > > or a patch you
> > > > could apply which introduced the 'not-so-efficient' code
> > > back again until
> > > > people are given a chance to upgrade.
> > > >
> > > > It may not be worth the effort if too complicated, or if
> > > noone shouts out
> > > > saying they can't upgrade, etc.
> > > >
> > > > /Mark
> > > >
> > > > > -----Original Message-----
> > > > > From: dbmail-dev-bounces@dbmail.org
> > > > > [mailto:dbmail-dev-bounces@dbmail.org] On Behalf Of Aaron Stone
> > > > > Sent: Monday, 15 March 2004 1:01 a.m.
> > > > > To: dbmail-dev@dbmail.org
> > > > > Subject: [Dbmail-dev] Bunch of fixes and improvements, but
> > > > > with a catch
> > > > >
> > > > >
> > > > > Hey,
> > > > >
> > > > > So I was reading through the sorting code, and realized that
> > > > > the copy of each
> > > > > message from the temporary delivery user to the destination
> > > > > user was much more
> > > > > expensive than I thought. I have rewritten db_copymsg() to
> > > > > use just 3 queries,
> > > > > where it used to be something like 10 queries!
> > > > >
> > > > > The catch is that MySQL 4.0.14 or higher is required because
> > > > > prior to 4.0.14,
> > > > > an INSERT INTO table1 ... SELECT FROM table2, where table1 ==
> > > > > table2, was not
> > > > > allowed. All versions of PostgreSQL support this SQL92
> > > > > compliant query, though.
> > > > >
> > > > > IMHO, this is a really important feature and it is well worth
> > > > > excluding those
> > > > > earlier MySQL versions to get support for it; Ilja, is that
> > > > > OK with you?
> > > > >
> > > > > Aaron
> > > > > _______________________________________________
> > > > > 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
> > >
> >
> > _______________________________________________
> > 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
>


--
Feargal Reilly,
Codeshifter,
Chrysalink Systems.