Extra MySQLisms to document in the hackers' guide: Bit arithmetic. auto_increment fields. tinytext, etc ?
Auto updating field types such as timestamp. When updating a row with a TIMESTAMP type, the column is automatically set to the current time even if the column is not directly accessed. This happens with updates and inserts. Also the TIMESTAMP column can only be set to now() or NULL. Certain date arithmetic is also only available for MySQL. Other DB's have to use extra functions that can convert a date to the necessary before performing the date arithmatic. MySQL also has the auto_increment feature which others do not. PostgreSQL comes close be providing the SERIAL data type which automatically sets up a sequence table for you and sets the default value for the primary key column to be the next value from the sequence table. Oracle doesnt have a SERIAL type but can be set up similarly by hand.
Might be useful to get lists for Oracle and PostgreSQL too, if we're going to support them soonish.
We are currently trying to wrap up Bugzilla 2.16. We are now close enough to release time that anything that wasn't already ranked at P1 isn't going to make the cut. Thus this is being retargetted at 2.18. If you strongly disagree with this retargetting, please comment, however, be aware that we only have about 2 weeks left to review and test anything at this point, and we intend to devote this time to the remaining bugs that were designated as release blockers.
The docs should always be up-to-date when we release. Forgot to exclude Documentation when I mass-retargetted.
I don't know enough about this to document it fully. Anybody want to submit a patch?
Others: Using " instead of ' internally REPLACE INTO is a mysqlism, and should be replaced by a check if the row is there, and then either an insert or an update.
I'll whip something up once you've whacked all the other bugs and can see how you've structured the new guide.
Moving process information bug to the web site component and taking them.
Most of this is in, with the exception of auto_increment (no alternative to recommend yet), and the SQL data types.
Unloved bugs targetted for 2.18 but untouched since 9-15-2003 are being retargeted to 2.20 If you plan to act on one immediately, go ahead and pull it back to 2.18.
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to email@example.com or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Now that we support MySQL, PostgreSQL and Oracle, I suppose we can close this bug? Our code is now pretty DB-independent.
As far as I can tell, this hackers' guide no longer exists, or has been integrated with the usual doc.