Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Wrong migration table usage in sqlite3.ensureVersionTable #165

New issue
New issue
Closed
#166
Closed
Wrong migration table usage in sqlite3.ensureVersionTable#165
#166
@bcho

Description

@bcho
bcho
opened on Feb 1, 2019

Describe the Bug

In

migrate/database/sqlite3/sqlite3.go

Lines 62 to 65 in f6d624c

query := fmt.Sprintf(`
CREATE TABLE IF NOT EXISTS %s (version uint64,dirty bool);
CREATE UNIQUE INDEX IF NOT EXISTS version_unique ON %s (version);
`, DefaultMigrationsTable, DefaultMigrationsTable)

we can easily find that the migration table used by ensureVersionTable is wrong.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions