SEO

#1 (**permalink**) 04-11-2008, 05:59 AM

Am trying to port a mysql statement to postgres.

Please help me in finding the error in this,

CREATE SEQUENCE ai_id;
CREATE TABLE badusers (
id int DEFAULT nextval('ai_id') NOT NULL,
UserName varchar(30),
Date datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
Reason varchar(200),
Admin varchar(30) DEFAULT '-',
PRIMARY KEY (id),
KEY UserName (UserName),
KEY Date (Date)
);

Am always getting foll. Errors,

ERROR: relation "ai_id" already exists
ERROR: syntax error at or near "(" at character 240

Thanks,
Rajesh R

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

#2 (**permalink**) 04-11-2008, 06:01 AM

On Thu, Sep 29, 2005 at 09:28:38PM +0800, Christopher Kings-Lynne wrote:
>
> >CREATE SEQUENCE ai_id;
> >CREATE TABLE badusers (
> > id int DEFAULT nextval('ai_id') NOT NULL,
> > UserName varchar(30),
> > Date datetime DEFAULT '0000-00-00 00:00:00' NOT NULL,
> > Reason varchar(200),
> > Admin varchar(30) DEFAULT '-',
> > PRIMARY KEY (id),
> > KEY UserName (UserName),
> > KEY Date (Date)
> >);
> >
> >
> >Am always getting foll. Errors,
> >
> >ERROR: relation "ai_id" already exists
> >ERROR: syntax error at or near "(" at character 240
>
> You have just copied the Mysql code to Postgresql. It will in no way
> work. Your default for 'Date' is illegal in postgresql and hence it
> must allow NULLs. There is no such thing as a 'datetime' type. There
> is no such thing as 'Key'. Also your mixed case identifiers won't be
> preserved. You want:
>
> CREATE TABLE badusers (
> id SERIAL PRIMARY KEY,
> UserName varchar(30),
> Date timestamp,
> Reason varchar(200),
> Admin varchar(30) DEFAULT '-'
> );
>
> CREATE INDEX UserName_Idx ON badusers(Username);
> CREATE INDEX Date_Idx ON badusers(Date);

Actually, to preserve the case you can wrap everything in quotes:
CREATE ...
"UserName" varchar(30)

Of course that means that now you have to do that in every statement
that uses that field, too...

SELECT username FROM badusers
ERROR

SELECT "UserName" FROM badusers
bad user

I suggest ditching the CamelCase and going with underline_seperators.
I'd also not use the bareword id, instead using bad_user_id. And I'd
name the table bad_user. But that's just me.

--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Query in SQL statement