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.

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

.clone failed when having table in a named schema #3995

Closed
rferraton opened this issue Jun 29, 2022 · 2 comments
Closed

.clone failed when having table in a named schema #3995

rferraton opened this issue Jun 29, 2022 · 2 comments
Labels

Comments

@rferraton
Copy link

What happens?

when cloning a connected database (using CLI and .clone command) that have one table in a "named" schema

To Reproduce

.open test_clone_seed.duckdb
create schema src;
create table src.test(col1 int);
.clone test_clone_clone.duckdb

Environment (please complete the following information):

  • OS: windows
  • DuckDB : 0.4.0
  • DuckDB Client : CLI

Identity Disclosure:

  • Full Name: Romain Ferraton
  • Affiliation: Architecture & Performance
@github-actions
Copy link

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale label Jul 30, 2023
@github-actions
Copy link

This issue was closed because it has been stale for 30 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant