On 22 February 2011 20:56, Guillaume Lelarge wrote:
> You're right. I added a ticket to work on this later.
I've noticed in the past that syntax highlighting is a bit broken.
It's possible to break it by copying and pasting. Perhaps I'll create
a test case for that if I get a chance later.
--
>Works for me here. What are your exact steps?
Steps to duplicate:
1. Right Click on a database
2. Click on Backup
3. In popup screen, specify filename.
4. Click the Objects Tab
5. Uncheck the database (1st box)
6. Specifically check two or more individu
Le 16/02/2011 14:21, Maximilian Tyrtania a écrit :
> Just found this in my log file:
>
> ERROR: invalid byte sequence for
> encoding "UTF8": 0xe3bc64
> STATEMENT: SELECT
> pg_file_read('pg_log/postgresql-2011-02-16_00.log', 10, 5)
>
> Still not sure what's going on there. Apparent
Le 16/02/2011 11:28, Jakob Egger a écrit :
> Syntax coloring in PgAdmin3 (Version 1.10.3 on MacOS) does not correctly deal
> with nested comments.
>
> Try entering the following in the "Query" window:
>
> /* /*NESTED COMMENT*/ THIS IS STILL A COMMENT */
>
> the words "THIS IS STILL A COMMENT"
Le 10/02/2011 22:37, Melvin Davidson a écrit :
> Guillaume,
>
> Thank you very much for your reply and contributions to PgAdmin!
>
You're welcome.
> FYI, In further testing of the backup, selective object backup is ignored,
> (options tab of backup) and all objects are backed up regardless.
>
