HiThe regression test cases for 'copy row' was failing.This patch was assuming that each selected row will have primary key due to selection was not working. Fixed.Please find revised patch.ThanksSurinder KumarOn Mon, May 15, 2017 at 1:13 PM, Surinder Kumar <surinder.kumar@enterprisedb.com> wrote:Hi,This patch contains following changes:1) When a new row is added, allow to delete if changes are not saved.2) Disable new row selection if primary key is not given but changes are saved on server.3) Copy and paste one or more rows, then add new row doesn't work(entered value doesn't appear).4) After deleting a row, add new row doesn't work.5) New row added with explicitly given primary key should not disabled.Please review.Thanks,Surinder Kumar -- Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org) To make changes to your subscription:http://www.postgresql.org/mailpref/pgadmin-hackers
Hi,This patch contains following changes:1) When a new row is added, allow to delete if changes are not saved.2) Disable new row selection if primary key is not given but changes are saved on server.3) Copy and paste one or more rows, then add new row doesn't work(entered value doesn't appear).4) After deleting a row, add new row doesn't work.5) New row added with explicitly given primary key should not disabled.Please review.Thanks,Surinder Kumar
pgadmin-hackers by date:
Соглашаюсь с условиями обработки персональных данных