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" <[EMAIL PROTECTED]> 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"" <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] 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" <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > > > > [mailto:[EMAIL PROTECTED] 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.
pgpvtg9lHqEkr.pgp
Description: PGP signature
