I am having problems reflecting tables in Oracle using cx_Oracle version 5.1 (autoload=True). Everything works fine under cx_Oracle version 5.0.4. Here's the error I get:
DatabaseError: (DatabaseError) ORA-01460: unimplemented or unreasonable conversion requested
Somehow, the query sent to oracle is not substituting the tablename and schema correctly. Has anybody seen anything like this and have a solution? I'd like to avoid to define columns manually for all the tables. I also want to use the latest versions if possible.
I just submitted a patch that fixes this issue for me. Support for Unicode was added to cx_Oracle and then later removed. There are a few lines in SQLAlchemy's cx_oracle.py that check the version of the cx_Oracle module. The patch updates these version checks to take into account the reverted Unicode support.
I think that it was your question that helped me get SQLAlchemy working with cx_Oracle for the first time a few weeks ago, so thanks for asking! :-D
As discussed in the thread for the patch of Alex, a solution is to set the NLS_LANG environment variable, so that cx_oracle can use the right converter. For example:
import os
os.environ["NLS_LANG"] = ".UTF8"
Related
I'm unable to utilize SQLite window functions (e.g. LAG, LEAD). After some investigation it seems that this is due to the fact that SQLite database version is below 3.25.0, after which window functions were made available.
Database created using SQLite 3.30.1 version
However version 3.24.0 version displayed on this 'test' database
When queries which include window functions are tested, such as the ones provided on sqlitetutorial site: the following errors are displayed
Could you please advise how to resolve this. I would much appreciate your support on this.
SELECT CustomerId, Year, Total,
LAG (Total, 1, 0) OVER (ORDER BY Year) PreviousYearTotal
FROM CustomerInvoices
WHERE CustomerId = 4;
Had this same issue. It looks like you're using SQLiteStudio, the latest version is 3.21 from December 2019. While your database was made in SQLite 3.30 (and your software is probably using 3.30), the version of SQLiteStudio you are using is based on 3.24.
There is an outstanding feature request to implement window functions in SQLiteStudio. Until then, the best you can do is replace the sqlite3.dll in the SQLiteStudio program directory with a newer version (3.30 , 32-bit works). Window functions will show as a syntax error, but the queries will still execute.
I'm having issues connecting to my MongoDB via Mongolite, and I'm not sure if it is an issue on my side, or if I need to use a different package to connect to the database. Please keep in mind that I cannot change the software being run by the MongoDB server, and I am a novice when it comes to all of this, so it could just be a silly error on my part.
I've run the following code:
m <- mongo(collection = "test", url="mongodb://22.92.59.149:27017")
As far as I can tell from the Mongolite tutorial (https://jeroen.github.io/mongolite/), this is the correct syntax to connect to the database, but I'm not 100% sure. Regardless, I get the following error:
Error: Server at 22.92.59.149:27017 reports wire version 2,
but this version of libmongoc requires at least 3 (MongoDB 3.0)
From what I can tell, this means that mongolite won't work with my database. If that is the case, what other package should I try to use to connect, or if it is not the issue what am I doing wrong?
Thanks in advance!
As the message says, there is a mismatch between versions of the client and the server.
More precisely, mongolite relies on a more general driver written in C, libmongoc, and it seems the version automatically installed by the install.packages("mongolite") statement is too recent towards the server's version.
If you can't change anything server-side, maybe you could try to manually install an older version of libmongoc before installing mongolite, but I'm not confident about the compatibility with that R package afterwards.
Maybe you can use RMongo, an older and archived package to interact with Mongo in R, but I'm afraid what you're going to develop won't be stable in further R versions.
I'd rather recommend you to look at the problem server side.
Here is a screenshot of the error occuring when I try to download the file using a button as described here:
IR to MSEXCEL Manual
Can anybody show me a step-by-step way of solving this? I really want to learn troubleshooting in APEX.
EDIT: Here is a screenshot of XML_TO_XLSX.sqf at line 851:
EDIT 2:
Link to Github Issue
I also have this plug-in in my application (working fine). According to the error message you show there is a problem at line 851 of body of package XML_TO_XSLX. You can look at this package code to see what that line does. In my copy (which may be a different version to yours, I don't know) I see:
That would suggest that Oracle could not find dbms_lob.create_temporary - which seems unlikely unless you are running in a very old version of Oracle. Have a look at your version of XML_TO_XSLX to see what is at line 851 there.
Another possibility is that line:
pragma inline(get_excel,'YES');
That is an feature of Oracle added in 11G that I have never used. It won't work on earlier versions - I have no idea what would happen if you tried.
I have found a solution myself, tt was an issue with execution rights.
Running
GRANT EXECUTE ON UTL_FILE TO PUBLIC
and recompiling all packages fixed it.
If I want to edit & rerun the previous command in sqlite3, presently I have to retype the query from scratch. It doesn't seem to support the 'arrow key' method you often get in terminal programs.
Running on Ubuntu.
Am I missing something?
In windows and ubuntu up key works fine.
Readline support must be enabled. Clean easy solution is here:
https://superuser.com/a/82447/87610
I just updated my Windows Phone 8 project to use the latest version of SQLite. I made sure to update the sqlite-net-wp8 package as well to use the latest version.
Now when I execute an update statement, I get an exception from the db: SQL logic error or missing database
This worked fine with 3.8.1. Is there any way I can go back?
If you try uninstall the old version to use it and the problem persist, maybe you can fix this looking at your Query...
After googling with an old bug that I've fixed before, I found this ...
SQLite3::SQLException: SQL logic error or missing database
After usual googling around and trying to fix it I just saw what the problem with the Query is.