The least I can say is that it *really* lacks informations.
On Wed, 2011-09-14 at 16:15 +0200, pasman pasmański wrote:
> 1. Error when deleting parent table.
>
Great, which error? and which steps brought you to that error?
> 2. Options of foreign table can't be set.
>
Works for me. Why can't
1. Error when deleting parent table.
2. Options of foreign table can't be set.
--
pasman
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
On Mon, Dec 20, 2010 at 4:37 AM, Benoygopal wrote:
> Dear PgAdmin Support Team,
>
> In our research and implementation projects we are using postgres database
> and pgadmin client as the front end.
> Our application and database are deployed in linux RHEL , Ubuntu and Windows.
> Using our applic
Dave Page <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Just out of curiosity, why is pgAdmin doing it this way at all?
>> Seems it would be a lot easier to use the all-columns form of
>> pg_get_indexdef than to cons up the display from fetches of each
>> column individually.
> We use the data
Dave Page <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Hm, there is a definitional issue here. Should pg_get_indexdef print
>> this stuff at all when colno is nonzero?
>> ...
>> Dave, I think we put in this variant of the function for pgAdmin ---
>> what does pgAdmin need?
> More is better fo
NikhilS <[EMAIL PROTECTED]> writes:
>> Looks like pg_get_indexdef is unwell :-(
> yes, it was unwell in the area where the amcanorder was being processed. The
> attached patch should fix this.
Hm, there is a definitional issue here. Should pg_get_indexdef print
this stuff at all when colno is no
Hello
it's pgAdmin bug. please report it there
Regards
Pavel Stehule
On 19/12/2007, Boonchai <[EMAIL PROTECTED]> wrote:
>
> The following bug has been logged online:
>
> Bug reference: 3829
> Logged by: Boonchai
> Email address: [EMAIL PROTECTED]
> PostgreSQL version: 8.3 beta
> -Original Message-
> From: BillR [mailto:[EMAIL PROTECTED]
> Sent: 29 November 2005 20:50
> To: Dave Page
> Subject: Re: [pgadmin-support] bugs in Query tool... case
> sensitivity conflict with the rest of PgAdmin created
> object... explicit schema
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of BillR
> Sent: 28 November 2005 22:59
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] bugs in Query tool... case
> sensitivity conflict with the rest of PgAd
OS: Windows 2000
PgAdmin III V 1.4
English
Binary (With PostgreSQL 8.1)
First: Thanks for making PgAdmin. It has prompted me to use PostgreSQL
much more.
Issues and steps to create the issues follow:
1) There is a conflict between how the 'automated' tools work and how
the Query tool works
KÖPFERL Robert wrote:
Maybe I'm telling old stories... if so, it's just the case.
I enountered couriosities while working with DOMAINS
When defining an aditional CHECK-constraint, the generated SQL looks like
that:
-- Domain: msisdn_type
-- DROP DOMAIN msisdn_type;
CREATE DOMAIN msisdn_type
AS va
Maybe I'm telling old stories... if so, it's just the case.
I enountered couriosities while working with DOMAINS
When defining an aditional CHECK-constraint, the generated SQL looks like
that:
>
-- Domain: msisdn_type
-- DROP DOMAIN msisdn_type;
CREATE DOMAIN msisdn_type
AS varchar(32)
CHEC
Alexandr S wrote:
Next bug.
--with full russian version of Pgadmin 3.1 (with russian title of
column and russian inserted data) : there is problem when selecting,
inserting relatively large block of data (for example , excerpt of
some text about 100 words size and more). Pgadmin suddenly ends
Next bug.
--with full russian version of Pgadmin 3.1 (with russian title of column
and russian inserted data) : there is problem when selecting, inserting
relatively large block of data (for example , excerpt of some text about
100 words size and more). Pgadmin suddenly ends to work and then I
I like this team very much.
pgAdmin, too.
Then, I think about how to enjoy it.
All of the members of the team were very great.
I will learn from there.
Then, I am proud to be this member.!!
From: "Andreas Pflug" <[EMAIL PROTECTED]>
> Dave Page wrote:
>
> >>-Original Message-
> >>From: And
Dave Page wrote:
-Original Message-
From: Andreas Pflug [mailto:[EMAIL PROTECTED]
Sent: 04 October 2003 10:43
To: Hiroshi Saito
Cc: [EMAIL PROTECTED]
Subject: Re: [pgadmin-support] [BUGS] bug reporting
Actually, it was an enhanced patch.
So I noticed!
Like usual, Hiroshi
> -Original Message-
> From: Andreas Pflug [mailto:[EMAIL PROTECTED]
> Sent: 04 October 2003 10:43
> To: Hiroshi Saito
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] [BUGS] bug reporting
>
> Actually, it was an enhanced patch.
So I noticed!
> Li
You are a target for the time being.
:-)
regrads,
Hiroshi Saito
- Original Message -
From: "Andreas Pflug" <[EMAIL PROTECTED]>
> Dave Page wrote:
>
> >Hi Hiroshi,
> >
> >Andreas said he'd already fixed it so I didn't apply your patch. I can see the fix
> >in both branches.
> >
> >Rega
Dave Page wrote:
Hi Hiroshi,
Andreas said he'd already fixed it so I didn't apply your patch. I can see the fix in both branches.
Regards, Dave.
Actually, it was an enhanced patch. Like usual, Hiroshi points me to a
problem, and I find another on the same line of source.
Regards,
Andreas
--
gt; Cc: Dave Page; [EMAIL PROTECTED]
> Subject: Re: [pgadmin-support] [BUGS] bug reporting
>
>
> Hi Andreas.
>
> I take the report that it looks like this in Japan.
> It was a problem with Windows.
> There is patch which I suggested before.
> It is important though this
Hi Andreas.
I take the report that it looks like this in Japan.
It was a problem with Windows.
There is patch which I suggested before.
It is important though this was ignored.
See it again.
OT)
My server is in bad condition, and I haven't been able to talk well since yesterday.
:-(
regards,
Hir
Alexandr S wrote:
Pgadmin 3.1 don t work (operations like insert rows) with columns
named in russian language (title of column in russian language). But
the same operations using PhpPgAdmin - all works very well, right.
And if replace russian title of column with equivalent in english -
all
Title: Message
Hi
Donald
-Original Message-From: Donald Fraser
[mailto:[EMAIL PROTECTED]] Sent: 18 December 2002
17:19To: [EMAIL PROTECTED]Subject:
[pgadmin-support] Bugs
Hi Dave,
I was investigating the trigger arguments bug
that I reported yesterday and in doing
Hi Dave,
I was investigating the trigger arguments bug that
I reported yesterday and in doing so have found another bug.
1)
Set show system objects;
Open the database 'template1';
Open Schema pg_catalog;
Select table pg_trigger;
Right click on the mouse button and select from
pop-up menu 'Vi
24 matches
Mail list logo
