Problem description: connecting to oracle using tns-names. (ok!) trying a simple query : select * from usr; receiving an error like this : ----------------------------------- De SQL-opdracht die deze fout veroorzaakt is: SELECT * FROM "usr" ----------------------------------- Steps to reproduce: 1. connect to oracle 2. type in a simple sql query in the sql designer 3. execute the query by clicking the database execute query icon Current behavior: The sqlBuilder is putting himself double-quotes arround the table-name. Oracle doesn't like this, and I don't know how to prevent the builder to add his own fantasies to my query. Expected behavior: Execute my sql statement as is. Operating System: Windows 7 Version: 4.2.2.1 release
You could change the query and set the execution to direct SQL. The text wouldn't be changed. But you couldn't add any value to the query. Which connection do you use to oracle? Could be there is a possibility to change this in the connection-settings.
It's just a strange way of doing things. I'm not used to get my sql-string changed by a carrying pgm. So, if I mistype, an error should be send back from Oracle ( or any other db). But, if my sql-string is erroneously changed by the carrying pgm, then I can not use that pgm ( libre-office base in this case ), because, whatever I do, it will always go on putting double quotes in my sql-string. I'm using the native oracle tns-names, which works fine. I have no knowledge of any 'strip off double quotes'-parameter in a connection to a db. change this in the connection settings? I'm passing a very ordinary, most simple connectionstring to Oracle, and the connection is setup without any trouble. Anyway, this is not a problem to me, I was just trying out your stuff. I furthermore like Libreoffice very much ! bugzilla-daemon@freedesktop.org schreef op 10/04/2014 20:39: > robert@familiegrosskopf.de <mailto:robert@familiegrosskopf.de> changed > bug 77169 <https://bugs.freedesktop.org/show_bug.cgi?id=77169> > What Removed Added > CC robert@familiegrosskopf.de > > *Comment # 1 <https://bugs.freedesktop.org/show_bug.cgi?id=77169#c1> > on bug 77169 <https://bugs.freedesktop.org/show_bug.cgi?id=77169> from > robert@familiegrosskopf.de <mailto:robert@familiegrosskopf.de> * > You could change the query and set the execution to direct SQL. The text > wouldn't be changed. But you couldn't add any value to the query. > > Which connection do you use to oracle? Could be there is a possibility to > change this in the connection-settings. > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. >
Let me try again. I have asked which connection you are using for oracle. Do you use JDBC or ODBC? Did you try to use the queries in direct SQL-mode (switch from design-mode to the code and press the SQL-button. The code won't be touched by the GUI any more.)?
For the connection I'm using the ADO OLE-DB interface, which then allows me to fill in the Oracle tns-name and so on. Indeed in SQL direct it works, but only if I give the tablenames in uppercase. ok to me, but... thanks. ----- Oorspronkelijk bericht ----- Van: bugzilla-daemon@freedesktop.org Aan: johannesjanssens@telenet.be Verzonden: Vrijdag 11 april 2014 19:03:19 Onderwerp: [Bug 77169] EDITING: Query builder (design), added double quotes. Comment # 3 on bug 77169 from robert@familiegrosskopf.de Let me try again. I have asked which connection you are using for oracle. Do you use JDBC or ODBC? Did you try to use the queries in direct SQL-mode (switch from design-mode to the code and press the SQL-button. The code won't be touched by the GUI any more.)? You are receiving this mail because: * You reported the bug.
Johannes, I wonder where the lower-case table name came from in the first place? Did Query Builder take it upon itself to lower-case the name? Terry.
Adding self to CC if not already on
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team This NEEDINFO message was generated on: 2015-07-18
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO Message generated on: 2015-09-03