On 03/08/2012 12:06 AM, Shigeru Hanada wrote:
> I think that makes, and will make sense. Because SQL/MED standard
> mentions about schema for only foreign table in "4.12 SQL-schemas" section.
>
> FYI, pgAdmin III shows them as a tree like:
>
> Database
> FDW
> Server
> User Mapping
>
Hi,
We've been discussing the subject in the pyrseas-general ML, but I think
it would be beneficial to get feedback from a broader audience.
The Pyrseas dbtoyaml utility outputs the objects in YAML, which ends up
looking like a tree (see
http://pyrseas.readthedocs.org/en/latest/dbtoyaml.html ) an
On 10/22/2011 04:31 PM, Alexander Farber wrote:
> Hello,
>
> sadly I have to ban few users from my game web
> site daily and so I'm trying to write a procedure for
> first copying their id, name, city, IP into a pref_ban table
> and then erasing their comments and statistics:
>
> create o
On 10/20/2011 05:10 PM, J.V. wrote:
> Is there a simpler way than this to query the database for meta-data and
> get the constraint definitions?
>
> If I have the constraint name (which I do), I could store the constraint
> definition to a file or database table and recreate them if I could get
>
On 10/11/2011 06:54 PM, J.V. wrote:
> If I have a table name, I know how to find the primary key constraint
> name, but see no way to find the primary key field name.
>
> select constraint_name from information_schema.tabale_constraints where
> table_name = and constraint_type = 'PRIMARY KEY';
>
On 10/11/2011 05:16 PM, J.V. wrote:
> I need to be able to query for all primary keys and save the table name
> and the name of the primary key field into some structure that I can
> iterate through later.
>
> How would I go about this? I want to hard code the number of tables and
> be able to it
On 10/05/2011 04:49 AM, depst...@alliedtesting.com wrote:
>> -Original Message-
>> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-
>> ow...@postgresql.org] On Behalf Of J.V.
>> Sent: Tuesday, October 04, 2011 10:00 PM
>> To: pgsql-general
>> Subject: [GENERAL] how to disable
On 10/04/2011 08:05 AM, Robert Buckley wrote:
> Thanks for the replies,
>
> I have one question regarding this comment...
>
> "You also need to add a DEFAULT expression and optionally
> make the sequence owned by the column:"
>
> What difference does it make if a table "owns" a sequence of not?.
On 10/03/2011 04:14 AM, Sim Zacks wrote:
> I don't know if there is an official definition, but an extension is
> generally a compiled program that is accessed by the SQL. It must be
> compiled with the postgresql headers and have the magic number defined.
> The compiled file must then be put into
Hi Sim,
On 10/02/2011 08:02 AM, Sim Zacks wrote:
> If I understand plpython correctly, it uses the python installed on the
> machine. In other words, plpythonu doesn't support the new style
> classes, it depends on what version of python is installed.
Well, Python has had new style classes since
Hi,
I'm toying with the idea of making the Pyrseas utilities a true
PostgreSQL extension. Currently, the utilities (dbtoyaml and yamltodb)
rely on a library of Python functions: over 16 modules and 4000+ lines
of code. The programs would remain as Python command line front-ends,
but there would b
HI Tom,
On 03/18/2011 12:42 AM, Joe Abbate wrote:
For my immediate needs, the query was actually the target of a NOT IN
subquery of a query against pg_index (trying to exclude tuples of
indexes for UNIQUE constraints) and I've solved that by using conrelid
in the subquery (and indrelid i
Hi Tom,
On 03/18/2011 12:17 AM, Tom Lane wrote:
Joe Abbate writes:
I'm using this to validate a tool I'm building and I get an error on the
following query:
autodoc=> SELECT conname::regclass FROM pg_constraint
autodoc->WHERE contype = '
Hi,
I'm using the autodoc regression database available at
http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/autodoc/autodoc/regressdatabase.sql?rev=1.2&content-type=text/x-cvsweb-markup
This has several schemas that have cross-schema foreign key constraints
such as the following:
autodoc=> \d pr
I currently maintain a website which is deployed on LAMP, but it is developed on
Windows (WAMP?). I'm considering moving both to use PostgreSQL. I'm curious as
to whether others are following a similar development/deployment model and if
so, what pitfalls/gotchas they have found. For example,
15 matches
Mail list logo
