Re: SVN Commit by dpage: r7544 - in trunk/pgadmin3: . pgadmin/frm pgadmin/include/utils pgadmin/ui - Mailing list pgadmin-hackers

From Quan Zongliang
Subject Re: SVN Commit by dpage: r7544 - in trunk/pgadmin3: . pgadmin/frm pgadmin/include/utils pgadmin/ui
Date
Msg-id 20090110115321.8E40.4125B4E5@gmail.com
Whole thread Raw
In response to SVN Commit by dpage: r7544 - in trunk/pgadmin3: . pgadmin/frm pgadmin/include/utils pgadmin/ui  (svn@pgadmin.org)
List pgadmin-hackers
> Add an option to ignore server version mismatches with pg_dump/pg_dumpall/pg_restore.

Why don't add this option to backup and restore dialogs?
And use option in frmOptions as default value.
I think it will make end users feel more convenient and more happy. ^_^

Along with this topic,
I had tried to use old-version pgadmin (1.6.3) connect to newer db (8.3 & 8.4).
When click the schema node, get a error message complain
column op.oprlsortop does not exist (maybe its name changed in newer version).
Now, we have BackendMinimumVersion function to confirm backward-compatible.
Clearly, it is needed that confirm forward-compatible.
We can give a upper limit version to individual pgadmin version.
When end users wanna connect to newer db, they will get a warning message or hint.

-----------------------------------------------
Quan Zongliang
quanzongliang@gmail.com
CIT Japan:  http://www.cit.co.jp
CIT China:  http://www.citbj.com.cn


pgadmin-hackers by date:

Previous
From: "Matteo Bertini"
Date:
Subject: PATCH: Limit 100 default in frmEditGrid.cpp
Next
From: Ashesh Vashi
Date:
Subject: Re: Need suggestion for showing boolean parameters on Property Dialogs