Alexander Steffens wrote:
> Dear Developpers,
>
> I found a (at least on my machine) 100% reproducible Exception
> NT_STATUS_INVALID_PARAMETER(0xc00d)
> when I enable the operator-tree and then click on operator %.
>
> My computer is a Windows 2003 R2 x64, I get the exception on
> pgAdminIII
Dear Developpers,
I found a (at least on my machine) 100% reproducible Exception
NT_STATUS_INVALID_PARAMETER(0xc00d)
when I enable the operator-tree and then click on operator %.
My computer is a Windows 2003 R2 x64, I get the exception on
pgAdminIII 1.6.2 and 1.8.0,
others i have not tried.
Setup: running on platform Suse Linux 9.1, language - en-us, distribution used
- v 1.0.2 (not sure whether source, tarball or binary)
All queries in the query tool hang. When the query tool window is closed,
pgadmin III crashes. If the query is a create or drop table(s), the query
works, but
[EMAIL PROTECTED] wrote:
The default behavior in pgsql is to allow the use of transactions to
isolate SQL statements. PgAdmin seems to batch the entire script into a
single transaction, making the user's transaction irrelevant.
Use the mailing list!
To pgAdmin, all you execute is a single statem
[EMAIL PROTECTED] wrote:
I'm trying to run a SQL script in pgAdminIII which works in psql but
fails in pgAdminIII
Platform: XP Professional sp2
Language: English
Distribution: pgadmin3-win32.zip 12-Sep-2004 19:34
Version: 1.2.0 Post Beta 1 (Sep 12 2004)
Problem:
The script I'm running drops
I'm trying to run a SQL script in pgAdminIII which works in psql but fails
in pgAdminIII
Platform: XP Professional sp2
Language: English
Distribution: pgadmin3-win32.zip 12-Sep-2004 19:34
Version: 1.2.0 Post Beta 1 (Sep 12 2004)
Problem:
The script I'm running drops a table, then creates
When I declare a function with a schema-qualified return type, PgAdmin does
not show the schema in the return type:
Here's what I tell Postgres:
===
CREATE OR REPLACE FUNCTION xxx.packet_data(pg_catalog.numeric, pg_catalog.text)
RETURNS setof xxx.data
Matej Rizman wrote:
PgAdmin III 0.9.0 BETA 1 (Aug 6 2003) on Windows XP
Description: I cannot enter lowercase or uppercase characters š and ž
(Slovenian letters: s with hachek and z with hachek) in query tool. I can
enter this character in other text boxes. If I switch keyboard layout to
English
PgAdmin III 0.9.0 BETA 1 (Aug 6 2003) on Windows XP
Description: I cannot enter lowercase or uppercase characters š and ž
(Slovenian letters: s with hachek and z with hachek) in query tool. I can
enter this character in other text boxes. If I switch keyboard layout to
English and press this key (
Matej Rizman wrote:
Version: pgAdmin III 0.8.0 Devel (Aug 3 2003)
After dropping database that is being accessed by other users pgAdmin III
shows message box and crashes.
Could you explain this more in detail? How is it dropped? Did it succeed?
Regards,
Andreas
---
Version: pgAdmin III 0.8.0 Devel (Aug 3 2003)
After dropping database that is being accessed by other users pgAdmin III
shows message box and crashes.
Regards,
Matej Rizman
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
Matej Rizman wrote:
Version: PgAdmin III 0.8.0 Devel (Jul 30 2003)
Adding NOT NULL columns or columns with default values to existing tables
does not work. Reason: PgAdmin III creates unsupported version of ALTER
TABLE SQL statement.
Thanks,
fixed in CVS.
Regards,
Andreas
Matej Rizman wrote:
Version: PgAdmin III 0.8.0 Devel (Jul 30 2003)
Platform: Windows XP
To reproduce this error do the following steps:
1) select table that has varchar column with some long text in it,
2) right click on this table and select "View data",
3) double click on previously mentioned lo
Matej Rizman wrote:
Version: pgAdmin III 0.8.0 Devel (Jul 30 2003)
Steps:
1) open pgAdmin III, go to arbitrary table and select its constraints
2) add new constraint with empty name (i.e. leave field Name empty)
Result: added constraint is not shown in list of constraints and you have to
refresh
Version: PgAdmin III 0.8.0 Devel (Jul 30 2003)
Platform: Windows XP
To reproduce this error do the following steps:
1) select table that has varchar column with some long text in it,
2) right click on this table and select "View data",
3) double click on previously mentioned long text,
4) press r
Version: pgAdmin III 0.8.0 Devel (Jul 30 2003)
Steps:
1) open pgAdmin III, go to arbitrary table and select its constraints
2) add new constraint with empty name (i.e. leave field Name empty)
Result: added constraint is not shown in list of constraints and you have to
refresh constraints tree no
Version: PgAdmin III 0.8.0 Devel (Jul 30 2003)
Adding NOT NULL columns or columns with default values to existing tables
does not work. Reason: PgAdmin III creates unsupported version of ALTER
TABLE SQL statement.
Regards,
Matej Rizman
---(end of broadcast)---
> Donald Fraser wrote:
>
> > pgAdmin III July 16th Build
> > PostgreSQL 7.3.3
> >
> > The reverse engineered SQL for indexes that use a function do not work.
> > For example I create an index with the following command:
> > CREATE UNIQUE INDEX tbl_security_fullname_key
> > ON tbl_security
> > U
Donald Fraser wrote:
pgAdmin III July 16th Build
PostgreSQL 7.3.3
The reverse engineered SQL for indexes that use a function do not work.
For example I create an index with the following command:
CREATE UNIQUE INDEX tbl_security_fullname_key
ON tbl_security
USING btree (get_securityname_4idx
pgAdmin III July 16th Build
PostgreSQL 7.3.3
The reverse engineered SQL for indexes that use a
function do not work.
For example I create an index with the following
command:
CREATE UNIQUE INDEX
tbl_security_fullname_key ON tbl_security USING
btree (get_securityname_4idx(s_umbname, s_nam
20 matches
Mail list logo
