Roland Martin wrote:
> Hi Dave,
>
> Mmm, OK. Thanks for your helpful response.
>
> Trouble, in this case, means that it can't be done. I do the following:
> 1. Locate any geometry_columns table
> 2. Right click -> View data (or view all rows in the submenu, or whatever)
> 3. I click in a field in
Roland Martin wrote:
> Hi,
>
> I'm going to reinstall the earlier version, since it does actually work.
> If anyone is ever interested in fixing this bug, please get in touch.
I fully intend to look at it, unfortunately sometimes I simply don't
have time to turn around bug fixes immediately in fr
Hi,
I'm going to reinstall the earlier version, since it does actually work. If
anyone is ever interested in fixing this bug, please get in touch.
Cheers,
Roland.
On 04/06/07, Roland Martin <[EMAIL PROTECTED]> wrote:
Hi Dave,
Mmm, OK. Thanks for your helpful response.
Trouble, in this cas
Hi Dave,
Mmm, OK. Thanks for your helpful response.
Trouble, in this case, means that it can't be done. I do the following:
1. Locate any geometry_columns table
2. Right click -> View data (or view all rows in the submenu, or whatever)
3. I click in a field in the f_table_name column, and make c
Roland Martin wrote:
> Hi,
>
> I've been having trouble editing a couple of tables in pgAdmin 1.6.3.
> The same operation works fine in 1.4.1, so I assume it's some sort of bug...
>
> The only tables (as far as I can tell) that are affected are PostGIS
> 'geometry_columns' tables. Before anyone a
Hi,
I've been having trouble editing a couple of tables in pgAdmin 1.6.3. The
same operation works fine in 1.4.1, so I assume it's some sort of bug...
The only tables (as far as I can tell) that are affected are PostGIS
'geometry_columns' tables. Before anyone asks, they do have OIDs.
Is there
