Open
Conversation
…d then deleting previous output data) Fixed bad time stamp translations from sqlite back to mssql
…e data, only the schema Fix for bug in previous commie of --no_data, which didn't copy primary keys.
Author
|
There was a bug in the previous --no_data addition. Primary keys were not being copied into the new schemas. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The --no_data [table name] argument will copy only the schema, but not any data for the named table. It works similar to the --skip argument in that it can be issued multiple times in a single command line.
Use case for this is transferring an MSSQL database with tables with many rows that you don't need in the sqlite version, but you do need the empty schema.