Importing SQL is not working
Chris Bell 3 years ago • updated 3 years ago • 6
I'm trying to create a new model based off of an SQL file, but when I try to upload the file I get a 500 error with this message:
Internal server error. Details command: new_physical_model_upload_sql_create, error-instanceId: OTH7FF7E7FF.RRINSRKQ.202003241742.0301
Customer support service by UserEcho
Could you please send to email@example.com your model?
Hi, I just saw this.
What do you mean my model? The SQL script files that I'm trying to import from? I just tried again, this time using an MSSQL script file. The previous times were SQLite3 files. I'm getting the same error with both.
message: "Internal server error. Details command: new_physical_model_upload_sql_create, error-instanceId: OTH7FF7E7FF.1TZLGTWG.202004151448.0201"
I've tried in Firefox, Chrome and Edge. Nothing works.
Yes, I meant the SQL script file. Sorry for not being precise enough.
I think that our app is not properly processing files not encoded with UTF-8. Since files are not processed properly they are not stored and I can't reproduce the error. That is why I am asking for the SQL script.
BTW, May I ask you what OS do you use?
Yep, that was the problem. The files I was trying to import were formatted as UTF-16LE, which is how the databases exported them. One was an SQLite3 script and one was an MSSQL script. Re-saving them as UTF-8 allowed them to be imported.
There's another thing that confused me when trying to work through this. In the web interface, I was able to create a new SQL script and save it in the "My Vertabelo" documents. So I did that and then copy-pasted my SQL script into there. But when I tried to create a new database, I couldn't find any way generate it from a script saved in the "My Vertabelo" documents, it only allowed me to choose one from my computer. Is there a way to do this that I missed? If not, I'm not sure what the purpose of the "Create new SQL script" feature is.
Thank you for the details of the problem. We will try to fix it.
You have not missed anything. There is no way to do that. Your idea is great. I wonder why we have not implemented it :)
The SQL script editor had more options, ie. executing on a database. To be honest, we have abandoned some of them because they caused more problems than profits. Since then, we have suspended the development of "SQL script" part.
Gotcha, that makes sense. Thanks for the info!