DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
	b=QpDR01ysVu4+/6thIKvmDadyw3+MgpeKYefc2pbFzdaIIqAYQneArL8ua9gFXzkHLif6rR8/o+9uQXmjbtduGOWWZCyeOqH2J74PPTiXOo0rB32E0THM4XtWxNhTyZy9hZ7Z0r3gKYZu4UCb20PGNnCvYyybIzPr7NpQgeLhtUw=;
Date: Sun, 27 Apr 2008 16:33:26 -0700 (PDT)
From: chester c young <chestercyoung@yahoo.com>
Subject: Re: psql: no schema info 
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: sql pgsql <pgsql-sql@postgresql.org>
In-Reply-To: <23267.1209335819@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Message-ID: <213749.31261.qm@web54304.mail.re2.yahoo.com>


> > however, just got burnt big time on sequences!  need to qualify
> them as
> > well, eg
> >   col1 integer default nextval( 'schema1.seq1' )
> 
> Move to something newer than 8.0.x, and this is automatic (because
> nextval's argument is actually a regclass constant).
> 
> 			regards, tom lane

using 8.2 and 8.3

here's (psychological) problem as I see it:

# set search_path=old_schema;
#
# create sequence new_schema.seq1;
#
# create table new_schema.table1(
#    col1 integer default nextval( 'seq1' )
# );

using old_schema.seq1, not new_schema.seq1

and imho to make matters more difficult to troubleshoot:

# \dt table1 -> does not show which schema for seq1


      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ