Created attachment 130288 [details]
Open the database and try the code as described for get the last inserted AutoValue
Open the attached Firebird 3 database.
Open Tools > SQL...
Mark "Show output of "select" statements.
Copy the following code:
INSERT INTO "Table" ("Name", "Town") VALUES ('Mike', 'Alexandria')
RETURNING "ID", "Name", "Town";
There is no value shown as output. The status shows only "1."
Expected is in "output":
There is a function in HSQLDB named "CALL IDENTITY()" This gives you the last inserted AutoValue. I hope to find this in Firebird. There it should run with RETURNING, but doesn't run in Tools > SQL... Will test this later with macros to see, if it's a problem of internal Firebird or a problem of the SQL-dialog.
Build ID: 92a1ad1f36b6d3cc13135a8c0805508933011577
CPU Threads: 4; OS Version: Windows 6.19; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2017-01-06_23:42:59
Have tested this with a macro. Firebird returns nothing to Base except a "." So there couldn't be tested the last input and the last inserted AutoValue.
All tested with
Build ID: a3cf075880db31f77cd0550e0ee25eca931c6a40
CPU Threads: 4; OS Version: Linux 4.1; UI Render: default; VCL: kde4;
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-01-05_01:21:50
Locale: de-DE (de_DE.UTF-8); Calc: group
(In reply to robert from comment #2)
> Have tested this with a macro.
Could you please share the macro? Did you use executeQuery or execute? (I assume not executeUpdate...)
Created attachment 138875 [details]
Testdatabase, also with code executed by macro: Input data works, returns nothing
It's only the same way as executed in Tools > SQL. Code is executed and returns nothing, so the macro couldn't find an object, only a "."
(In reply to Lionel Elie Mamane from comment #3)
> Could you please share the macro? Did you use executeQuery or execute? (I
> assume not executeUpdate...)
Did use executeQuery, because I need a result.
By the way: very much people helping hunting and solving Base-bugs last week. Great!
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Bug still exists. Tested with
Build ID: 0412ee99e862f384c1106d0841a950c4cfaa9df1
CPU threads: 6; OS: Linux 4.12; UI render: default; VCL: gtk3;
Locale: de-DE (de_DE.UTF-8); UI-Language: en-US
Also with LO 22.214.171.124 on OpenSUSE 64bit rpm Linux
Created attachment 153043 [details]
New Testdatabase - old database seems to be broken.
During a crash in bugzilla the database seems to be broken.
With LO 126.96.36.199 the Update-command returns '0 rows updated' - which is totally wrong. There has been added a row. RETURNING should show the content of the added row.
With LO 188.8.131.52 the whole LO crashes immediately after sending the command to the database.
All tested with OpenSUSE 15 64bit rpm Linux