Raggaer
I am currently trying to import a .sql file containing database tables on an Ecto migration, basically my Phoenix application adds some extra funcionality to the given database, so I need to import it:
defmodule XXX.Repo.Migrations.XXX do
use Ecto.Migration
def change do
execute File.read!("schema.sql")
end
end
However the migration fails, complaining its not valid SQL, the migration success if my .sql file only contains one table to create, when I add more the syntax fails for some reason…
The file is valid SQL and it works just fine doing “mysql -u root -p XX < file.sql” or even copy/paste into terminal. This is the file I am trying to import https://hastebin.com/zifosewayi.sql
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 5- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dimitarvp
No clue why it’s failing – I think I remember it only accepts one SQL statement but I wouldn’t bet my life on it.
One thing you could try is splitting the SQL at the
;delimiter and then loop over the results and execute them one by one?John-Goff
You could also use the
--dump-pathoption for mix ecto.load — Ecto SQL v3.14.0, doesn’t fully solve the problem of rerunning it. But I personally set up an alias in my mix.exs to run our “base” SQL file and then migrations after that.Raggaer
That seems to work, strange limitation, thank you
Raggaer
I will try that approach, my problem was indeed rerunning but just modifying the flow of
ecto.resetshould be enough for me, thank youhauleth
It is limitation of prepared statements which are used internally in Ecto. This is security measure among other things.