Re: [Lazarus] LazDataDesktop: transaction handling

2019-09-05 Thread Ondrej Pokorny via lazarus
On 05.09.2019 8:20, Michael Van Canneyt via lazarus wrote: The grid was never meant to be editable. I simply forgot to disable that. (I myself never ever edit in a grid, it didn't appear in my head that someone would do this) But I will : a) Add the sqoAutoApplyUpdates option. b) Add buttons

Re: [Lazarus] LazDataDesktop: transaction handling

2019-09-05 Thread Michael Van Canneyt via lazarus
On Thu, 5 Sep 2019, LacaK via lazarus wrote: If data of underlaying TSQLQuery are presented and edited only thorought this DBGrid then I would add to TSQLQuery option "sqoAutoApplyUpdates". (I am not familiar with architecture of LazDataDesktop) Which causes that on every Post/Delete updates

Re: [Lazarus] LazDataDesktop: transaction handling

2019-09-04 Thread LacaK via lazarus
If data of underlaying TSQLQuery are presented and edited only thorought this DBGrid then I would add to TSQLQuery option "sqoAutoApplyUpdates". (I am not familiar with architecture of LazDataDesktop) Which causes that on every Post/Delete updates are applied to database. There will remain

[Lazarus] LazDataDesktop: transaction handling

2019-09-04 Thread Ondrej Pokorny via lazarus
Hello (Michael)! I started to use LazDataDesktop because PgAdmin4 is horrible. I have a problem with transactions with Postgres connection (well I tested only Postgres connection). I found out that when using the SQL editor, I can type "COMMIT" and "ROLLBACK" - so far so good. (Well I would