Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

--drop-existing doesn't work with dbt seed #515

Closed
jthandy opened this issue Aug 22, 2017 · 3 comments
Closed

--drop-existing doesn't work with dbt seed #515

jthandy opened this issue Aug 22, 2017 · 3 comments
Milestone
0.9.2

Comments

@jthandy
Copy link
Member

jthandy commented Aug 22, 2017

when attempting to recreate tables that had previously been built with dbt seed, an error message shows saying that the table already exists.
@drewbanin
Copy link
Contributor

drewbanin commented Aug 22, 2017 •
edited
Loading

This can happen if there's a view with the same name as the csv file. Do you think that's what's happening here @jthandy? The --drop-existing flag logic looks like correct otherwise.

drewbanin added a commit that referenced this issue Aug 22, 2017
@drewbanin
Fixes #515
10e1b52
@drewbanin drewbanin mentioned this issue Aug 22, 2017
Closed
@jthandy
Copy link
Member Author

jthandy commented Aug 22, 2017

totally possible, i'm not sure.

@drewbanin drewbanin added this to the 0.9.2 milestone Jan 12, 2018
@drewbanin
Copy link
Contributor

--drop-existing is now deprecated, use --full-refresh instead.

We overhauled dbt's implementation of seed -- This particular error is handled by alerting the user that they're running a seed file with the same name as a view in the database.

https://github.com/fishtown-analytics/dbt/blob/development/dbt/adapters/default.py#L637

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.9.2
Development

No branches or pull requests
2 participants
@drewbanin @jthandy