pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedReasonable
4+ messages / 4 participants
[nested] [flat]
* Reasonable
@ 1999-10-05 15:32 Mitch Vincent <mitch@venux.net>
0 siblings, 2 replies; 4+ messages in thread
From: Mitch Vincent @ 1999-10-05 15:32 UTC (permalink / raw)
To: pgsql-sql
It seems that this below is causing some strange problems with our
PostgreSQL database. We're running it on a FreeBSD 3.2 box, PG version 6.5.1
(with a 6.5.2 upgrade planned really soon)
These seems good to me, I can't see any errors yet when I try to enter it
into a database, it either locks up psql (the client) or just does nothing
at all..
As you can see from the format it is from a pg_dump of another datatable, I
just added a few things and was going to turn around and create another
table, then the problems started.. If the error is something simple then I
do apologize for wasting anyone's time, however I can't seem to see anything
wrong..
Thanks!!
The query that's giving me fits :
CREATE TABLE "user_applicant_search" (
"app_id" int4,
"created" datetime,
"createdcond" varying(2),
"status" character varying(1) default 'Active',
"statuscond" character varying(1) default '=',
"firstname" character varying(25),
"firstnamecond" character varying(2) default '=',
"lastname" character varying(25),
"lastnamecond" character varying(2) default '=',
"address1" character varying(30),
"address1cond" character varying(2) default '=',
"address2" character varying(30),
"city" character varying(20),
"citycond" character varying(8) default 'starts',
"state" character varying(10),
"statecond" character varying(2) default '=',
"email" character varying(50),
"emailcond character varying(8) default 'starts',
"clearance" character varying(20),
"clearancecond" character varying(8) default 'starts',
"language" character varying(20),
"languagecond" character varying(8) default 'starts',
"dateavailable" date,
"dateavailablecond" varying(2) default '=',
"employed" bool,
"employedcond" character varying(1) default 'X',
"sic1" int4,
"sic1cond" character varying(2) default '>=',
"skill1" int4,
"skill1cond" character varying(2) default '>=',
"coregroup" character varying(10),
"coregroupcond" character varying(8) default 'starts',
"objective" character varying(80),
"objectivecond" character varying(8) default 'starts',
"degree1" character varying(30),
"degree1cond" character varying(8) default 'starts',
"d1type" character varying(6),
"d1typecond" character varying(2) default '=',
"d1discipline" character varying(30),
"d1disciplinecond" character varying(3) default '=',
"d1date" int4,
"d1datecond" character varying(2) default '=',
"d1gpa" float,
"d1gpacond" character varying(2) default '=',
"salary" character varying(40),
"salarycond" character varying(8) default 'starts',
"salarycurrent" int4,
"salarycurrentcond" character varying(2) default '=',
"salarydesire" int4,
"salarydesirecond" character varying(2) default '=',
"salarymin" int4,
"salarymincond" character varying(2) default '=',
"license" character varying(50),
"licensecond" character varying(8) default 'starts',
"locstate" character varying(2),
"locstatecond" character varying(8) default 'contains');
Again, thanks!!
- Mitch
"0100110100110000010101000100001101001000"
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [SQL] Reasonable
@ 1999-10-05 16:23 Albert REINER <areiner@tph.tuwien.ac.at>
parent: Mitch Vincent <mitch@venux.net>
1 sibling, 0 replies; 4+ messages in thread
From: Albert REINER @ 1999-10-05 16:23 UTC (permalink / raw)
To: pgsql-sql
On Tue, Oct 05, 1999 at 11:32:50AM -0400, Mitch Vincent wrote:
...
> The query that's giving me fits :
>
>
>
> CREATE TABLE "user_applicant_search" (
> "app_id" int4,
> "created" datetime,
> "createdcond" varying(2),
> "status" character varying(1) default 'Active',
> "statuscond" character varying(1) default '=',
> "firstname" character varying(25),
> "firstnamecond" character varying(2) default '=',
> "lastname" character varying(25),
> "lastnamecond" character varying(2) default '=',
> "address1" character varying(30),
> "address1cond" character varying(2) default '=',
> "address2" character varying(30),
> "city" character varying(20),
> "citycond" character varying(8) default 'starts',
> "state" character varying(10),
> "statecond" character varying(2) default '=',
> "email" character varying(50),
> "emailcond character varying(8) default 'starts',
... ^^^^^^
Don't you need a closing "?
Albert.
--
---------------------------------------------------------------------------
Post an / Mail to / Skribu al: Albert Reiner <areiner@tph.tuwien.ac.at>
---------------------------------------------------------------------------
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [SQL] Reasonable
@ 1999-10-05 16:32 Herouth Maoz <herouth@oumail.openu.ac.il>
parent: Mitch Vincent <mitch@venux.net>
1 sibling, 1 reply; 4+ messages in thread
From: Herouth Maoz @ 1999-10-05 16:32 UTC (permalink / raw)
To: Mitch Vincent <mitch@venux.net>; pgsql-sql
At 17:32 +0200 on 05/10/1999, Mitch Vincent wrote:
...
> "createdcond" varying(2),
> "status" character varying(1) default 'Active',
> "statuscond" character varying(1) default '=',
> "firstname" character varying(25),
> "firstnamecond" character varying(2) default '=',
> "lastname" character varying(25),
> "lastnamecond" character varying(2) default '=',
> "address1" character varying(30),
> "address1cond" character varying(2) default '=',
> "address2" character varying(30),
> "city" character varying(20),
> "citycond" character varying(8) default 'starts',
...
It's hard to know when you don't tell us which error message you got, but
my guess is as follows: Most of these fields are defined using the syntax
"fieldname" character varying(N)...
But I seem to detect a couple of fields, "createdcond" above, as well as
"dateavailablecond". Are those the fields you added? For some reason, they
are defined as:
"fieldname" varying(N)...
Without the character keyword. On a cursory look this would not work.
Another potential problem is your use of a six-letter long default for a
varying(1) field ("status").
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [SQL] Reasonable
@ 1999-10-05 23:10 Tom Lane <tgl@sss.pgh.pa.us>
parent: Herouth Maoz <herouth@oumail.openu.ac.il>
0 siblings, 0 replies; 4+ messages in thread
From: Tom Lane @ 1999-10-05 23:10 UTC (permalink / raw)
To: Herouth Maoz <herouth@oumail.openu.ac.il>; +Cc: Mitch Vincent <mitch@venux.net>; pgsql-sql
Herouth Maoz <herouth@oumail.openu.ac.il> writes:
> Another potential problem is your use of a six-letter long default for a
> varying(1) field ("status").
6.5.* has some problems with wrong-length default values for char(n) and
varchar(n) fields. There is a slightly klugy fix in place for char(n),
but a cursory test suggests that it doesn't catch the varchar case.
The consequences aren't as bad as they were for char(n): you just get
a field value that's longer than it's supposed to be. Workaround:
give a correct default value.
This is all fixed properly in current sources (6.6/7.0-to-be).
regards, tom lane
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~1999-10-05 23:10 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-10-05 15:32 Reasonable Mitch Vincent <mitch@venux.net>
1999-10-05 16:23 ` Albert REINER <areiner@tph.tuwien.ac.at>
1999-10-05 16:32 ` Herouth Maoz <herouth@oumail.openu.ac.il>
1999-10-05 23:10 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox