On 5/07/2012 3:57 AM, Guillaume Lelarge wrote:
On Tue, 2012-07-03 at 14:50 +0800, Rohan Carly wrote:
On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
I have taken to making a copy of the password file so that when the
connection fails
On 5/07/2012 3:57 AM, Guillaume Lelarge wrote:
On Tue, 2012-07-03 at 14:50 +0800, Rohan Carly wrote:
On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
I have taken to making a copy of the password file so that when the
connection fails
On 3/07/2012 4:09 PM, Dave Page wrote:
On Tue, Jul 3, 2012 at 8:38 AM, Rohan Carly wrote:
In pgAdmin III v.1.14.1, if you navigate to
schemas/public/tables//Columns/ and right-click on the column
name and press "create script", you often get a script that will not
execute.
The prob
In pgAdmin III v.1.14.1, if you navigate to
schemas/public/tables//Columns/ and right-click on the column
name and press "create script", you often get a script that will not execute.
The problem occurs when you have a column that has "NOT NULL" and a "DEFAULT"
property.
e.g. A script genera
On 17/02/2012 6:33 AM, Guillaume Lelarge wrote:
On Wed, 2012-02-15 at 05:16 -0600, Michael Shapiro wrote:
I have taken to making a copy of the password file so that when the
connection fails and PgAdmin removes the password, I can put it back.
I think I've found your issue. Here is the way to
ll create implicit index
>'name_table_pkey' f
>or table 'name_table'
>NOTICE: ALTER TABLE will create implicit trigger(s) for FOREIGN KEY
check(s)
>ERROR: parser: parse error at or near "("
>NOTICE: ROLLBACK: no transaction in progress
I hav
