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

crash then correct table #390

Closed
PKEv opened this issue Jul 27, 2015 · 11 comments
Closed

crash then correct table #390

PKEv opened this issue Jul 27, 2015 · 11 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs.

Comments

@PKEv
Copy link

PKEv commented Jul 27, 2015

to repeat:

  1. create table,with some column
  2. click "correct table"
  3. add some column
  4. move any column
    default
    (update)
@justinclift
Copy link
Member

Sounds like a bug, though I don't understand Russian personally so someone else will have to figure it out. 😉

@justinclift justinclift added the bug Confirmed bugs or reports that are very likely to be bugs. label Jul 29, 2015
@gordeyg
Copy link
Contributor

gordeyg commented Aug 3, 2015

Following information provided in russian: "Column rename: error releasing (freeing?) savepoint. DB says: [..] "

@justinclift
Copy link
Member

Thanks @GeorgijK.

@MKleusberg Any ideas?

MKleusberg added a commit that referenced this issue Aug 6, 2015
@MKleusberg
Fix error message when renaming/moving/modifying column
ce40d55 
When modifying a column e.g. renaming it there was a case where an error
message would be shown because of invalid SAVEPOINT handling. Try to fix
this issue by not creating a SAVEPOINT for creating a SAVEPOINT.

This should fix issue #390.
@MKleusberg
Copy link
Member

I've looked into this and with any luck it should be fixed in the next nightly build 😃 Let us know how if the fix works for you, @GeorgijK 😄

@MKleusberg
Copy link
Member

Oops, I ment @PKEv of course. Let us know if the next nightly build fixes your problem, @PKEv 😃

@justinclift
Copy link
Member

@PKEv Do you have time to check the latest nightly build? 😄

@PKEv
Copy link
Author

PKEv commented Aug 12, 2015

test ver. from 12-Aug-2015
error persists

@justinclift
Copy link
Member

@PKEv Thanks for testing. 😄

@MKleusberg Looks like we still have work to do. 😦

MKleusberg pushed a commit that referenced this issue Oct 14, 2015
@gordeyg @MKleusberg
Fixed bug issue #390 ("crash then correct table").
9d7efca 
Some functions renamed for better readability.

See pull request #401.
@MKleusberg
Copy link
Member

@PKEv Are you ok to test if the bug still occurs in the latest nightly build? To me it looks like it should be fixed by now 😄

@PKEv
Copy link
Author

PKEv commented Dec 24, 2015

corrected!!!

@PKEv PKEv closed this as completed Dec 24, 2015
@justinclift
Copy link
Member

Awesome. 😄

@chrisjlocke chrisjlocke mentioned this issue Nov 28, 2016
Closed
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Confirmed bugs or reports that are very likely to be bugs.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@justinclift @gordeyg @MKleusberg @PKEv