On Wed, 8 Jun 2005 21:57:25 -0600
"George Sexton" <gsexton@stripped> wrote:
> I think MySQL has a little ways to go yet before I would
> subjectively call it best.
> I posted twice to the list with questions about porting my
> application that runs on (SQL Server, Oracle, PostgreSQL, Sybase SQL
> Anywhere, MS Access, and DB2) to MySQL. No one on the mysql list, or
> the internals list responded to my pretty basic issues:
> 1) Why can't I declare a datetime field with DEFAULT NOW()
"The DEFAULT clause specifies a default value for a column. With one
exception, the default value must be a constant; it cannot be a
function or an expression. This means, for example, that you cannot
set the default for a date column to be the value of a function such
as NOW() or CURRENT_DATE. The exception is that you can specify
CURRENT_TIMESTAMP as the default for a TIMESTAMP column as of MySQL
4.1.2. See Section 126.96.36.199, _TIMESTAMP Properties as of MySQL 4.1_. "
"For date and time types other than TIMESTAMP, the default is the
appropriate ``zero'' value for the type. For the first TIMESTAMP
column in a table, the default value is the current date and time. See
Section 11.3, _Date and Time Types_. "
Looks like a policy decision, not a missing feature? Why does the
TIMESTAMP column not meet your needs?
> 2) Since the SQL standard states that identifiers are not case
> sensitive, how can I use the DB without case sensitivity, when I
> don't have authority to change the system wide lowercase setting? I
> wouldn't have authority to change the setting in a hosted
Only thing I would suggest is to work with your hosting admin to see
if they would be willing to change this system-wide setting since
there is no per-user control over this. If this is something you
cannot live with then choose a different RDBMS.
> I have to say, MySQL still looks like a tinker-toy to me.
<ignoring troll bait>