-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warnings while creating SQLite database #6
Comments
And you did the setup step to "create" your database, as recommended in Setup? ( |
Forgot to add, as per the Setup instructions: And you created the tables with |
|
Seems very peculiar indeed, then. When I have some time to spare, I can try checking if medic still works with OSX and/or Linux. However, note, I have no access to Windows machines. |
I tested on OS X (High Sierra, 10.13.1 (17B48)) and get the same warnings. I wonder if this has to do with differences in the versions of sqlalchemy we are using. Here is info for my system.
|
Could totally be the case; When I developed and worked with this tool, it still was version 0.8 (see the setup.py). |
Confirmed. Sadly that means something in SQLAlchemy has changed sufficiently to break backwards compatibility. As I don't have enough time to spend on fixing that level of detail, I guess that has put medic out of service. PRs that fix this welcome, while I am sorry to say that I have no ETA on when I can get this fixed. |
If it helps, for anyone looking into this, I just tried the various SQLAlchemy versions, including 0.8 that was around when I developed this tool, and none of them fixes the problem. So I guess it's some change to SQLite or the Python API of the same. |
I greatly appreciate all of the time you already put into this software and understand your time constraints. |
Well, as I tried building medic in environment with all SQLAlchemy versions back to 0.8, and no-one works, I have my doubts that is a SQLAlchemy problem at all. Because it seems weird why this issue would pop up now, but never popped before using the same earlier versions (I think I was using, e.g., 0.9, pretty nicely. But yes, I could be wrong on that count, e.g., if medic was working due to some bug in SQLAlchemy that got patched in later versions of the 0.8 release. |
BTW, if I'm correct, medic still should work with PostrgreSQL. |
That is odd. It seems like the messages are emitted by SQLAlchemy, but perhaps those are a side effect of changes to sqlite/pysqlite. |
I faced a similar problem for baseline 2020 data, and found there is no DateCreated terms in current pubmed DTD.
|
As my understanding, |
Hi,
Your program
medic
looks extremely useful.I am trying to create a medline sql database using files downloaded from
ftp://ftp.ncbi.nlm.nih.gov/pubmed/baseline
.After the download, I issue the following shell command:
For each file, I get the following database table-related warnings:
Platform: Windows 7
Medic: 2.4.1
Python: Python 3.6.3 |Anaconda custom (64-bit)|
The text was updated successfully, but these errors were encountered: