If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Hackers' Guide - Extra MySQLisms.

RESOLVED WORKSFORME

Status

()

Bugzilla
bugzilla.org
P2
normal
RESOLVED WORKSFORME
16 years ago
9 years ago

People

(Reporter: CodeMachine, Assigned: CodeMachine)

Tracking

Details

(Assignee)

Description

16 years ago
Extra MySQLisms to document in the hackers' guide:

Bit arithmetic.
auto_increment fields.
tinytext, etc ?

Comment 1

16 years ago
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.
(Assignee)

Comment 2

16 years ago
Might be useful to get lists for Oracle and PostgreSQL too, if we're going to
support them soonish.
(Assignee)

Updated

16 years ago
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.16
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.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
The docs should always be up-to-date when we release.  Forgot to exclude
Documentation when I mass-retargetted.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16

Comment 5

16 years ago
I don't know enough about this to document it fully.
Anybody want to submit a patch?
Status: NEW → ASSIGNED
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.
(Assignee)

Comment 7

16 years ago
I'll whip something up once you've whacked all the other bugs and can see how
you've structured the new guide.
(Assignee)

Comment 8

16 years ago
Moving process information bug to the web site component and taking them.
Assignee: barnboy → matty
Status: ASSIGNED → NEW
Component: Documentation → bugzilla.org
(Assignee)

Comment 9

16 years ago
Most of this is in, with the exception of auto_increment (no alternative to
recommend yet), and the SQL data types.
(Assignee)

Updated

16 years ago
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
ping

Comment 11

14 years ago
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.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20

Comment 12

13 years ago
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 nobody@bugzilla.org 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.
Target Milestone: Bugzilla 2.20 → ---

Updated

12 years ago
QA Contact: mattyt-bugzilla → default-qa

Comment 13

10 years ago
Now that we support MySQL, PostgreSQL and Oracle, I suppose we can close this bug? Our code is now pretty DB-independent.

Comment 14

9 years ago
As far as I can tell, this hackers' guide no longer exists, or has been integrated with the usual doc.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.