phpesp-general

[phpesp-general] phpESP 1.8.1 Initial Table Population SQL Error

[McDonald, J. M. <ja...@Ja...>]

db created correctly with the included SQL script.

Next I tried to create the tables with the appropriate script, but I kept
getting SQL errors:

ERROR 1064 at line 24: You have an error in your SQL syntax.  Check the
manual that corresponds to your MySQL server version for the right syntax
to use near 'CURRENT_TIMESTAMP,
        PRIMARY KEY(name)
)' at line 4

I have narrowed it down to the CURRENT_TIMESTAMP argument in all of the
tables; for instance:

CREATE TABLE realm (
        name            CHAR(16) NOT NULL,
        title           CHAR(64) NOT NULL,
        changed         TIMESTAMP(14) DEFAULT CURRENT_TIMESTAMP,
        PRIMARY KEY(name)
);

I have been reading the MySQL documentation and it seems that if the
TIMESTAMP record/column is created as NULL it will automagically default
to the current timestamp. The only other way I have been able to
circumvent this error is to enclose CURRENT_TIMESTAMP in ' ', such as
'CURRENT_TIMESTAMP' but I don't think that will do what is intended.

Does anyone have advice on how to resolve this error in the SQL script?
Should I just replace DEFAULT CURRENT_TIMESTAMP with NULL?

Jacob

Re: [phpesp-general] phpESP 1.8.1 Initial Table Population SQL Error

[Matthew G. <mat...@gm...>]

This was recently fixed.  Grab the latest version of the populate file from
Sourceforce CVS.

On 3/29/06, McDonald, Jacob M. <ja...@ja...> wrote:
>
> db created correctly with the included SQL script.
>
> Next I tried to create the tables with the appropriate script, but I kept
> getting SQL errors:
>
> ERROR 1064 at line 24: You have an error in your SQL syntax.  Check the
> manual that corresponds to your MySQL server version for the right syntax
> to use near 'CURRENT_TIMESTAMP,
>         PRIMARY KEY(name)
> )' at line 4
>
> I have narrowed it down to the CURRENT_TIMESTAMP argument in all of the
> tables; for instance:
>
> CREATE TABLE realm (
>         name            CHAR(16) NOT NULL,
>         title           CHAR(64) NOT NULL,
>         changed         TIMESTAMP(14) DEFAULT CURRENT_TIMESTAMP,
>         PRIMARY KEY(name)
> );
>
> I have been reading the MySQL documentation and it seems that if the
> TIMESTAMP record/column is created as NULL it will automagically default
> to the current timestamp. The only other way I have been able to
> circumvent this error is to enclose CURRENT_TIMESTAMP in ' ', such as
> 'CURRENT_TIMESTAMP' but I don't think that will do what is intended.
>
> Does anyone have advice on how to resolve this error in the SQL script?
> Should I just replace DEFAULT CURRENT_TIMESTAMP with NULL?
>
> Jacob
>
>
>


--
D'oh!