Skip to content

--all option confused by FTS tables #5

@simonw

Description

@simonw

Got this error:

% python -i -m sqlite_history content.db --all
Traceback (most recent call last):
  File "<frozen runpy>", line 198, in _run_module_as_main
  File "<frozen runpy>", line 88, in _run_code
  File "/Users/simon/Dropbox/Development/sqlite-history/sqlite_history/__main__.py", line 4, in <module>
    run()
  File "/Users/simon/Dropbox/Development/sqlite-history/sqlite_history/cli.py", line 67, in run
    configure_triggers(args.database_path, args.tables)
  File "/Users/simon/Dropbox/Development/sqlite-history/sqlite_history/cli.py", line 20, in configure_triggers
    configure_history(db, table)
  File "/Users/simon/Dropbox/Development/sqlite-history/sqlite_history/__init__.py", line 14, in configure_history
    db.execute(backfill_sql(table, columns))
sqlite3.OperationalError: no such column: rowid
>>> import pdb; pdb.pm()
> /Users/simon/Dropbox/Development/sqlite-history/sqlite_history/__init__.py(14)configure_history()
-> db.execute(backfill_sql(table, columns))
(Pdb) print(table)
releases_fts_idx
(Pdb) print(columns)
['segid', 'term', 'pgno']

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions