in reply to DBI and SQLite's .read feature
That said, it is probably not a good idea to try to process commands intended for the specific sqlite code file - because these commands can include several "." commands, including ".pause" , ".print", and various formatting directives that would make no sense to DBI.
You should consider separating your query from database creation.
If you still want to pursue this angle, there are a few (not recommended) options:
1) Use system calls or backticks to run sqlite externally, to process the .sql file.
2) Parse and extract the SELECT statement from the .sql file, and pass it into DBI.
...it is unhealthy to remain near things that are in the process of blowing up. man page for WARP, by Larry Wall
|
|---|