On Jun 3, 10:20 am, Kev wrote:
> On pgAdminIII 1.12.0 beta 1, I've been having this happen really
> frequently. One table I can't even edit--as soon as I type a single
> character in a column to make a new row, it crash-vanishes every
> time. Actually, it does an odd
On pgAdminIII 1.12.0 beta 1, I've been having this happen really
frequently. One table I can't even edit--as soon as I type a single
character in a column to make a new row, it crash-vanishes every
time. Actually, it does an odd thing before vanishing, creating a set
of horizontal and vertical sc
t succeeds, but the new one it fails. The command line strings
are identical.
What else is there for me to check?
Thanks in advance for your help,
Kev
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
When I create a table with a PK, and get a notice of the form:
NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index "(table)
_pkey" for table "(table)"
Indeed, the index it mentions shows up in pg_index. pgAdmin, however,
shows zero indices under the table, even after refreshing the ta
Whenever I have a standard 'raise notice' in one of my functions for
debugging, and I run a select statement on the function in the query,
the Messages pane only sometimes puts newlines after "NOTICE: ..."
lines, and if I just keep hitting F5, it's after different lines every
time. Often there are
On Sep 26, 12:34 pm, [EMAIL PROTECTED] (Erwin Brandstetter)
wrote:
> Hi Kev!
>
> Please send this to the list, not to my private email account:
>
> [EMAIL PROTECTED]
>
> Regards
> Erwin
Oh, no wonder...after a certain amount of time, there isn't actually a
&
but sometimes my brain doesn't gravitate towards the same
terminology other people might use to describe the same problem, so I
found nothing.
Thanks,
Kev
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
editor and then save again.
I could be wrong, but this sounds like a bug. Thoughts or
suggestions?
Thanks,
Kev
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support
Greetings,
On pgAdminIII 1.6, if you add a text column NOT NULL with a default of
a single space, it doesn't get quoted, and throws an error.
Kev
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an approp
