Hello,
Has something changed from 1.4 to 1.6 in how pgadmin exports files? In
1.6 RC1 I have had issues when exporting the results of a query to a
file that
A) I get the dialog box that says the Export completed sucessfully
B) Upon opening the file I find it is damaged because the results were
I have been working with PGAdminIII v1.6.1. and 1.6.2 for the past three
days and discovered a problem while editing. To reproduce the error, open
the editor window to edit an existing object. Then, place the insertion
point with the mouse somewhere where you want to edit the document. For the
sake
I am running on Win XP and I have permission. There are only some of the
tables in this condition. Once I enter info (through a Delphi interface) the
row appears - but only rows that have information. These tables also are
missing the column headers until info is entered.
This condition is pre
Can a pgsql 8.1 database be restored from the raw file? For one database
I have only the files found in the base folder, example C:\PostgreSQL
\data\base\16404, under that there are many files called 1247, 1248, etc
(no extension). I think these are the files that make up the database?
For this
PgAdmin 1.6.0
Windows XP (current SP/fixes)
postgresql 8.1.3 (also 7.x)
To recreate:
Highlight a table in the server browser. Choose a table that will
take a while to load in the table edit view.
Be sure View All is selected in the options.
Click on the edit table butto
novnov wrote:
It seems you're right, in all of my 7 or so tests I was seeing a
'disturbance in the force' that seemed to have a 1:1 correlation to the
nametype, but it turned out to be coincidental.
:-)
Yeah, the force can be unpredictable at times.
Regards, Dave.
-
novnov wrote:
> When 1.6 seems to have dropped varchar in favor of character varying.
> Shouldn't this be an option as opposed to an enforced behavior? I've read
> a
> little on the list about the change, but the problem is some packages I'm
> working with don't recognize character varying. Maybe
Bob Pawley wrote:
I just installed version 8.1 of PostgreSQL and version 1.6.1 of PG Admin.
In the new PG Admin some of the tables show blank (no columns, no
headings) and the row anticipating information is also not shown.
What OS are you running on? Do you have appropriate permissions to v
On 4 Dec 2006 at 11:50, Patrick Headley wrote:
> If you open one of the maintenance forms for backing up or restoring a
> database, the form isn't wide enough to display the browse button for
> selecting the file to backup into or restore from. I checked this on
I've encountered that tooyou
PGAdmin III v1.6.1 binary install
Windows XP SP2 with all known patches
This was an issue in v1.4.2, as well.
I can backup a PostgreSQL v8.0.4 database with large objects with no
problems. However, if I use PGAdminIII v1.6.1 to restore the database I
receive an error message when pg_restor
PGAdmin III v1.6.1 binary install
Windows XP SP2 with all known patches
If you open one of the maintenance forms for backing up or restoring a
database, the form isn't wide enough to display the browse button for
selecting the file to backup into or restore from. I checked this on v1.4.2
and i
I just installed PostgreSQL 8.1 and PG Admin 1.6.1 .
These versions have a sequential column, that is not part of the table,
identifying the rows.
Is there any method of accessing those numbers and identifying them with
elements within the table??
Bob Pawley
Thank you so much. Now everything is ok.
My real best regards
Ezequias Rodrigues da Rocha
2006/12/2, Melvin Davidson <[EMAIL PROTECTED]>:
Look at your script.
Your syntax is backward.
> GRANT administradores TO ezequias;
Also, you must create the administradores role _BEPORE_ you grant to i
I just installed version 8.1 of PostgreSQL and version 1.6.1 of PG Admin.
In the new PG Admin some of the tables show blank (no columns, no headings) and
the row anticipating information is also not shown.
In the older version, my method of testing triggers is to input the information
into the
Luca Ferrari wrote:
On Sunday 03 December 2006 20:42 Dave Page's cat, walking on the keyboard,
wrote:
Add --with-wx-version=2.8 to pgAdmin's configure command. 1.6 defaults
to 2.7.
That's worked, and I finally get pgadmin compiled. However, if I run it:
/usr/local/postgresql/pgadmin1.6.1/bin/
On Sunday 03 December 2006 20:42 Dave Page's cat, walking on the keyboard,
wrote:
>
> Add --with-wx-version=2.8 to pgAdmin's configure command. 1.6 defaults
> to 2.7.
That's worked, and I finally get pgadmin compiled. However, if I run it:
/usr/local/postgresql/pgadmin1.6.1/bin/pgadmin3
/usr/loc
please unsubscribe me.
i've been on this mailing list for 3 years now and i've never read the
mails.
please unscribe me.
_
Don't just search. Find. Check out the new MSN Search!
http://search.msn.com/
--
please unsubscrieb me .
> Date: Fri, 1 Dec 2006 00:31:25 -0800
> From: [EMAIL PROTECTED]
> Subject: [pgadmin-support] ./configure error
> To: pgadmin-support@postgresql.org
>
> Downloaded pgadmin1.4 to install. Already have wxGTK (and wxGTK-compat)
> 2.6.3.3
novnov wrote:
When 1.6 seems to have dropped varchar in favor of character varying.
Shouldn't this be an option as opposed to an enforced behavior? I've read a
little on the list about the change, but the problem is some packages I'm
working with don't recognize character varying. Maybe that will
19 matches
Mail list logo
