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

Moving Table To Different Schema and Back Again Causes Crash #1131

Closed
3 of 14 tasks
chrisjlocke opened this issue Sep 12, 2017 · 5 comments
Closed
3 of 14 tasks

Moving Table To Different Schema and Back Again Causes Crash #1131

chrisjlocke opened this issue Sep 12, 2017 · 5 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs. crash

Comments

@chrisjlocke
Copy link
Member

chrisjlocke commented Sep 12, 2017

Details for the issue

If a table from an attached database is moved to a different schema, it cannot be moved back to its original schema again otherwise DB4S crashes.
Guess it makes sense (maybe...) as I'm moving it back to where it came from, but there isn't anything there for it to slot into? No idea... just waffling....

https://screencast-o-matic.com/watch/cbQlIVIIsF

Useful extra information

I'm opening this issue because:

  • DB4S is crashing
  • DB4S has a bug
  • DB4S needs a feature
  • DB4S has another problem

I'm using DB4S on:

  • Windows: ( version: 10___ )
  • Linux: ( distro: ___ )
  • Mac OS: ( version: ___ )
  • Other: ___

I'm using DB4S version:

  • 3.10.0
  • 3.10.0-beta*
  • 3.9.1
  • Other: Nightly from 12 Sept_

I have also:

@justinclift
Copy link
Member

Definitely a bug. At a guess, something which should have been pointed to the new location hasn't been, and gets confused. Good catch @chrisjlocke. 😄

@justinclift justinclift added the bug Confirmed bugs or reports that are very likely to be bugs. label Sep 12, 2017
MKleusberg added a commit that referenced this issue Oct 5, 2017
Fix a crash which happened when opening a table in the Edit Table dialog
for modification and changing its schema and then (without reopening the
dialog) change the schema again or doing some other modifications to the
table.

See issue #1131.
@MKleusberg
Copy link
Member

Awesome, thanks for the screen recording. That actually helped a lot 😄 I think the issue is fixed now. Can you check the next nightly, @chrisjlocke? 😄

@chrisjlocke
Copy link
Member Author

Thanks ... will try tomorrow, or it might be Monday. Got a vet appointment tomorrow, so depends on how things go at work. :)

@chrisjlocke
Copy link
Member Author

chrisjlocke commented Oct 6, 2017

Excellent, thanks @MKleusberg ! Another issue squished. This works great.

@MKleusberg
Copy link
Member

Awesome 😄 Thanks for testing - and for finding this issue 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs. crash
Projects
None yet
Development

No branches or pull requests

3 participants