Found it: Re: Failure to save as postgresql database

2021-01-24 Thread Jack
On 2021.01.24 16:57, Jack wrote: On 2021.01.23 01:31, Thomas Baumgart wrote: On Samstag, 23. Januar 2021 02:00:46 CET Jack wrote: [snip] The actual current error is "Query error No 0: ERROR: current transaction is aborted, commands ignored until end of transaction block" so I'm now d

Re: Quick update: Re: Failure to save as postgresql database

2021-01-24 Thread Jack
On 2021.01.23 01:31, Thomas Baumgart wrote: On Samstag, 23. Januar 2021 02:00:46 CET Jack wrote: [snip] The actual current error is "Query error No 0: ERROR: current transaction is aborted, commands ignored until end of transaction block" so I'm now digging into tracking if there is a

Re: Quick update: Re: Failure to save as postgresql database

2021-01-22 Thread Thomas Baumgart
On Samstag, 23. Januar 2021 02:00:46 CET Jack wrote: > On 2021.01.01 13:57, Jack wrote: > > On 2020.12.31 19:02, Jack wrote: > >> In looking at https://bugs.kde.org/show_bug.cgi?id=430163 I got both > >> mariadb and postgresql set up. I can save to mariadb (mysql) but > >> not to postgresql.

Quick update: Re: Failure to save as postgresql database

2021-01-22 Thread Jack
On 2021.01.01 13:57, Jack wrote: On 2020.12.31 19:02, Jack wrote: In looking at https://bugs.kde.org/show_bug.cgi?id=430163 I got both mariadb and postgresql set up. I can save to mariadb (mysql) but not to postgresql. The error I get is: - Cannot save to current database: Error in fu

Re: Failure to save as postgresql database

2021-01-11 Thread Jack
Update on status, quoting below from different messages. On 2021.01.05 08:22, Thomas Baumgart wrote: On Dienstag, 5. Januar 2021 01:58:33 CET Jack wrote: This happens in qMakePreparedStmtId(). Since the stmtId in the failing case is empty, it must have been cleared or never set. The me

Re: Failure to save as postgresql database

2021-01-06 Thread Thomas Baumgart
On Mittwoch, 6. Januar 2021 01:14:32 CET Jack wrote: > On 2021.01.05 08:22, Thomas Baumgart wrote: > > I scanned the Qt source code and noticed, that the numerical suffix > > to qpsqlpstmt_ is to base 16 so hexadecimal. DE and F1 are perfect > > numbers then. > > [snip...] > > > So it seems

Re: Failure to save as postgresql database

2021-01-05 Thread Jack
On 2021.01.05 08:22, Thomas Baumgart wrote: I scanned the Qt source code and noticed, that the numerical suffix to qpsqlpstmt_ is to base 16 so hexadecimal. DE and F1 are perfect numbers then. [snip...] So it seems to me, that exec is called in the wrong spot. But the whole thing works for

Re: Failure to save as postgresql database

2021-01-05 Thread Thomas Baumgart
On Dienstag, 5. Januar 2021 01:58:33 CET Jack wrote: > On 2021.01.01 13:57, Jack wrote: > > On 2020.12.31 19:02, Jack wrote: > >> In looking at https://bugs.kde.org/show_bug.cgi?id=430163 I got both > >> mariadb and postgresql set up. I can save to mariadb (mysql) but > >> not to postgresql.

Re: Failure to save as postgresql database

2021-01-04 Thread Jack
On 2021.01.01 13:57, Jack wrote: On 2020.12.31 19:02, Jack wrote: In looking at https://bugs.kde.org/show_bug.cgi?id=430163 I got both mariadb and postgresql set up. I can save to mariadb (mysql) but not to postgresql. The error I get is: - Cannot save to current database: Error in fu

Re: Failure to save as postgresql database

2021-01-01 Thread Jack
On 2020.12.31 19:02, Jack wrote: In looking at https://bugs.kde.org/show_bug.cgi?id=430163 I got both mariadb and postgresql set up. I can save to mariadb (mysql) but not to postgresql. The error I get is: - Cannot save to current database: Error in function void MyMoneyStorageSqlPri