|
Hi
Alex,
This
is a known problem which is not the easiest to fix. In pgAdmin 1.2, whe updating
rows it built an SQL query based on virtually all columns in the row. This often
failed because of things like timezone differences or floating point errors. In
pgAdmin 1.4, it will now use a primary key if one is available which greatly
reduces the chance of error, however it doesn't handle multipart primary keys
:-(
This
is on my todo list, but I can't say when I will get to it...
Regards, Dave.
|
Title: Message
- [pgadmin-hackers] pgadmin2 1.4.12 edit record- update record Alex Balan
- Dave Page
