Erwin Brandstetter wrote:
The tablespace issue concerns primary key - and unique constraints.
This should have gone into a separate paragraph but got mixed up.
I have had another look at this.
On Indexes, the field "Tablespace" is generally deactivated (with pg 8.1
or 8.2). I do have an additi
Hi Dave!
Sounds like you've nailed issues with the big nail gun this morning. :)
Looking forward to the next version.
[EMAIL PROTECTED] wrote:
(...)
Erwin Brandstetter wrote:
The field "Tablespace" seems to do nothing at all. Choosing a
different tablespace does not activate the OK button
Erwin Brandstetter wrote:
> Very good! But some things are not right ..
Gah!!
> Testing Beta 3.5(Aug 29 2007, rev: 6584:6588M) on Win XP. Client Win XP,
> host: Debian Etch / PG 8.2.4 and Debian Sarge / PG 8.1.8.
> Everything concerns the table subtree.
>
>
> - Generally: either the focus jumps
Erwin Brandstetter wrote:
- Trying to add a comment to UNIQUE CONSTRAINT fails altogether.
Actually, it doesn't fail to write. It just doesn't show up anywhere in
pgadmin afterwards.
psql doesn't seem to have a meta-command to retrieve comments on
constraints. But checking by OID with "obj
[EMAIL PROTECTED] wrote:
OK, I figured out how to hierarchically retain the expanded/collapsed
state of the child nodes during refresh - turned out to be *much* easier
that I thought it would be.
I've updated the .exe again - please let me know what you think.
Very good! But some things are
Raymond O'Donnell wrote:
> On 29/08/2007 11:43, Dave Page wrote:
>
>> OK, I figured out how to hierarchically retain the expanded/collapsed
>> state of the child nodes during refresh - turned out to be *much* easier
>> that I thought it would be.
>
> I'm delighted that's been sorted - a small nig
On 29/08/2007 11:43, Dave Page wrote:
OK, I figured out how to hierarchically retain the expanded/collapsed
state of the child nodes during refresh - turned out to be *much* easier
that I thought it would be.
I'm delighted that's been sorted - a small niggle, but one which has
caught me once
Erwin Brandstetter wrote:
> [EMAIL PROTECTED] wrote:
>> Erwin Brandstetter wrote:
>>
>>> If any change via properties dialog would collapse the whole table
>>> subtree that would be a change for the worse IMO. Then I'd rather have
>>> the status quo ante.
>>> Is there no way to just refresh the S
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
If any change via properties dialog would collapse the whole table
subtree that would be a change for the worse IMO. Then I'd rather have
the status quo ante.
Is there no way to just refresh the SQL pane?
Not really - it's generated fr
Erwin Brandstetter wrote:
> Also applies to views. (column defaults ...)
It works for them as well.
>> the only downside being
>> that it causes the child collection nodes to get recreated which causes
>> them to become collapsed. Not sure how to fix that without a fairly
>> large rewrite.
>>
[EMAIL PROTECTED] wrote:
Erwin Brandstetter wrote:
(...)
Concerning the issue at hand I am unsure what to look for. What Martin
addressed in his initial posting seems fixed in any case. Other things
might remain to be addressed.
For instance: add a new field per dialog.
-> field shows up in "
Erwin Brandstetter wrote:
> Hi Dave!
>
> [EMAIL PROTECTED] wrote:
> (...)
>> I've changed the behaviour somewhat so that's probably a little out of
>> date. There are undoubtedly some corner cases which would be a nightmare
>> to catch, but let's see if you pick anything up first.
>>
>
> I am
Hi Dave!
[EMAIL PROTECTED] wrote:
(...)
I've changed the behaviour somewhat so that's probably a little out of
date. There are undoubtedly some corner cases which would be a nightmare
to catch, but let's see if you pick anything up first.
I am back on my feet again and have run a few tests
Erwin Brandstetter wrote:
> Hi Dave!
>
> [EMAIL PROTECTED] wrote:
>> (...)
>> Erwin; I'm somewhat wary of fixes in the treeview refresh code as there
>> can be odd corner cases caused by the relationships between some object
>> types. If I get you an updated exe, would you mind running it though
Hi Dave!
[EMAIL PROTECTED] wrote:
(...)
Erwin; I'm somewhat wary of fixes in the treeview refresh code as there
can be odd corner cases caused by the relationships between some object
types. If I get you an updated exe, would you mind running it though
it's paces to help check I didn't miss
Martin Serrano wrote:
> If there is a list of current bugs other than what appears in the help,
> please direct me to it.
>
> I'm using the Win32 version.
>
> 1) When adding a new column to a table, I have hit "refresh" on the
> table before the column is available within the add constraint dial
If there is a list of current bugs other than what appears in the help,
please direct me to it.
I'm using the Win32 version.
1) When adding a new column to a table, I have hit "refresh" on the table
before the column is available within the add constraint dialog.
Thanks,
Martin
17 matches
Mail list logo
