I can admit it might be handsome in some (lazy/amateur) usecases. But it shouldn't be used to drift requirements and user experience wrong way
best regards MK On 26.10.2016 17:19, André Cardoso wrote:
Reason to work with files stored on server: dump/backup fileDo you already worked with Microsoft SQL Server? If you do, then you know some things are more secure at server side than client side... IMHO...2016-10-26 13:00 GMT-02:00 Michal Kozusznik <kozusznik.mic...@ifortuna.cz <mailto:kozusznik.mic...@ifortuna.cz>>:On 26.10.2016 16:15, Dave Page wrote: Or a misunderstanding on your part on the goals of the project and reasons for them. So just list the reasons, please. IMO there is no single reason to work with files stored on the server. It could be even considered non-safe in some scenarios. It's enough to work with client-side files. It's valid for local as well as remote work I agree. Except where it is not possible to do so, or in cases where it could lead to an inconsistent UI experience. What do you mean by inconsistent UI experience? If you mean pgadmin having different file browser appearance across various operating systems then it's non-relevant argument. Goal should be to have UI-consistent app in environment it's running under. With client-app responsible for opening files approach, everything would work out together. with regards MK -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org <mailto:pgadmin-support@postgresql.org>) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support <http://www.postgresql.org/mailpref/pgadmin-support>
<<attachment: kozusznik_michal.vcf>>
-- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support