The parameter you give to the sqlite3 program is the database file name. To execute commands from a file, you must redirect the input to that file: $ sqlite3 mydatabase.db < SQLTableTransfer or tell it to read from that file: $ sqlite3 mydatabase.db “.read SQLTableTransfer”
Such -journal files do not need to (and should not) be distributed. This is because the various journal files represent temporary data (ref. SQLite’s Use Of Temporary Disk Files) used by SQLite. In particular a -journal file is a rollback journal. A rollback journal is a temporary file used to implement atomic commit and rollback … Read more
In Microsoft SQL Server, VARCHAR is ASCII and NVARCHAR is Unicode (UTF-16). In SQLite, all text is Unicode, so it’s not relevant. In any case, SQLite is loosely typed so it wouldn’t make a difference anyways. See http://www.sqlite.org/datatype3.html:)
this code is more general but maybe it can help you: import sqlite3 new_db = sqlite3.connect(‘:memory:’) # create a memory database old_db = sqlite3.connect(‘test.db’) query = “”.join(line for line in old_db.iterdump()) # Dump old database in the new one. new_db.executescript(query) EDIT : for getting your specify table you can just change in the for loop … Read more
You have this python code: c.execute(“insert into medicoes values(?,?,?,?,?,?,?)” % keys) which I think should be c.execute(“insert into medicoes values (?,?,?,?,?,?,?)”, keys) since the % operator expects the string to its left to contain formatting codes. Now all you need to make this work is for keys to be a tuple (or list) containing the … Read more
Yes. See the Join (SQL) > Outer join > Full outer join article on Wikipedia. SELECT employee.*, department.* FROM employee LEFT JOIN department ON employee.DepartmentID = department.DepartmentID UNION ALL SELECT employee.*, department.* FROM department LEFT JOIN employee ON employee.DepartmentID = department.DepartmentID WHERE employee.DepartmentID IS NULL
Here is the snippet that I wrote for my Flask application: import sqlite3 from io import StringIO def init_sqlite_db(app): # Read database to tempfile con = sqlite3.connect(app.config[‘SQLITE_DATABASE’]) tempfile = StringIO() for line in con.iterdump(): tempfile.write(‘%s\n’ % line) con.close() tempfile.seek(0) # Create a database in memory and import from tempfile app.sqlite = sqlite3.connect(“:memory:”) app.sqlite.cursor().executescript(tempfile.read()) app.sqlite.commit() app.sqlite.row_factory … Read more
Another solution is to precreate 100 rows and instead of INSERT use UPDATE to update the oldest row. Assuming that the table has a datetime field, the query UPDATE … WHERE datetime = (SELECT min(datetime) FROM logtable) can do the job. Edit: display the last 100 entries SELECT * FROM logtable ORDER BY datetime DESC … Read more
Prepared statements improve performance by caching the execution plan for a query after the query optimizer has found the best plan. If the query you’re using doesn’t have a complicated plan (such as simple selects/inserts with no joins), then prepared statements won’t give you a big improvement since the optimizer will quickly find the best … Read more