cool, SQL Workbench/J: does the job. It's too bad that it doesn't list the lables/views, so that you can't just open them with a click (i use select * from table to get the data), but it works well.
thanks Thomas. On Mon, Dec 9, 2013 at 11:51 PM, Thomas Kellerer <spam_ea...@gmx.net> wrote: > Willy-Bas Loos wrote on 09.12.2013 21:44: > > But the option to save the record is disabled, the other 2 buttons do not >> enable me to save the record. >> Anyway, i don't care much for MS Access, any client will do (that is, if >> it costs money, >> it would be nice if most users own it already or it isn't very expensive) >> >> I've tried: >> * pgAdmin >> * MS Access 2010 over ODBC >> * LibreOffice.org with the SDBC driver. >> >> Does anyone know of a client that is either smart enough to understand >> about rules on views, >> or transparent enough to let the server handle everything? >> > > If pgAdmin is acceptable, you might want to try SQL Workbench/J: > http://www.sql-workbench.net > > It will allow to run inserts on anything that you can select from and it > will prompt the user for the PK columns in case none could be identified in > the database (such as when updating the result of a select based on a view > or retrieving data from a table without a PK). The selection of the PK > columns can be saved (locally) to avoid further prompting > > Disclosure: I am the author of that tool. > > Regards > > Thomas > > > > > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > -- "Quality comes from focus and clarity of purpose" -- Mark Shuttleworth
