DOH, I see it in the subject now.
If you can get to a command line where the db server resides, you can use
the mysql client to do the import, or if phpmyadmin is available, you can
use its interface to import the dump. IIRC livecode doesn't like sending
multi-line sql to mysql (though it works in sqlite) so it might be possible
to parse the file line by line and send each line in sequence. (No clue
what other hoops you might need to jump through to do this though. )
On Wed, Feb 14, 2018 at 9:46 AM, Ludovic THEBAULT via use-livecode <
> > Le 14 févr. 2018 à 17:12, Mike Bonner via use-livecode <
> email@example.com> a écrit :
> > If this is sqlite, you might be able to use the .read dot command.. (note
> > the nearly invisible period that begins .read)
> > Untested, but this might work.
> > put "path/to/dump.sql" into tPath
> > put merge(".dump [[tpath]]") into tSql
> > revexecutesql tDatabaseId, tsql
> > If the dump is IN to sqlite, but is from another db (mySQL or whatever)
> > might not work.
> > Oh, if its sqlite and you still have access to the first database file,
> > should be possible to a) open the new database, b) attach the old
> > and c) copy the tables you need from one to the other, then d) detach the
> > old database and you should be good to go.
> Thanks, but it’s for Mysql.
> use-livecode mailing list
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription