<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - PostgreSQL JDBC: Autoincrement doesn't return values in Queries with Alias" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130376#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - PostgreSQL JDBC: Autoincrement doesn't return values in Queries with Alias" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130376">bug 130376</a> from <a class="email" href="mailto:mailinglisten@kmhessler.de" title="Michael <mailinglisten@kmhessler.de>"> Michael</a> <pre>Found the same here, using LO-BASE: Version: 6.1.5.2, Build-ID: 90f8dcf33c87b3705e78202e3df5142b201bd805, CPU-Threads: 4; BS: Linux 5.3; UI-Render: Standard; VCL: kde4; Gebietsschema: de-DE (de_DE.UTF-8); Calc: group threaded PostgreSQL: PostgreSQL 10.10 (Ubuntu 10.10-0ubuntu0.18.04.1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0, 64-bit Additional information: 1) All variants for SQL-queries, having an Alias-Name in the FROM-clause cause that entry in the PostgreSQL-Log-file and - as reported - the ID for new entries is shown as 0; entering more than one record at a time, you'll see multiple ID-values = 0 below each other. Having this fault, I also found issues in BASE-Forms or Queries, where sometimes one ore more data fields get lost on saving. 2) The same SQL-query without Alias-Name in the FROM-clause works fine without entry in the PostgreSQL-Log-file, the ID is shown correct no data fields get lost anymore. 3) Using the same SQL-query WITH Alias-Name in the FROM-clause in DBeaver works fine without entry in the PostgreSQL-Log-file or any other issue.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>