Database tool unable to commit any changes in 2016.3
已回答
I have a MySQL 5 database I've been viewing and editing in IDEA for a while. But when I bring up the table in 2016.3 I cannot seem to save any changes to the table?
If I make changes with autocommit on, then close the editor and reopen all changes I made are lost. The same thing happens if I hit reload after making changes.
If I turn off autocommit and make changes the commit button never enables to allow me to commit changes.
There's no errors in the database event log, even simple changes with no constraints (editing a string) seem not to work at all?
请先登录再写评论。
Hello Richard,
Please use Ctrl(Cmd)+Enter to submit changes to the database, see https://youtrack.jetbrains.com/issue/DBE-3500#comment=27-1744368 We will make this behavior more clear in the next update.
Wondering why the commit button wasn't enabled? if I had pending changes. The way its presented with the autocommit select box at the top of the datagrid is confusing. Why allow people to make a whole bunch of changes they then cannot commit? ctrl+enter in each cell? or just while in the form after making my all changes? it isn't at all intuitive.
Also note the datagrid "rememebr me" on the database login doesn't work, keeps asking for password every time I restart IDEA 2016.3 (on CentOS6).
After trying this its just ctrl+enter while the datagrid is active, not in any cell where it adds a newline to that cell.
Also note the commit button only enables after I hit ctrl+enter. i.e. after I've committed and there's nothing to commit? its state seems to be the opposite of what I'd expect.
Commit is also enabled after I refresh the grid - which also suggests its state is wired up wrong or it means something completely different to what I mean by an SQL commit.
>Also note the commit button only enables after I hit ctrl+enter. i.e. after I've committed and there's nothing to commit?
Commit button should be enable for this case only if you do not have Auto Commit option set. Then for committing submitted changes (since they are not Auto-committed) you need to press the commit. Does it make sense?
Not its not making sense to me.
What I see is if I turn autocommit off, make some changes the commit button is still disabled.
When I hit ctrl+enter to commit all my changes after that the commit button is suddenly enabled (nothing left to commit?) - or if I hit refresh and loose all my changes commit is enabled after that too.
When I actually have something that needs committing the button appears to be disabled? when I don't its enabled?
I also had trouble with this and only worked out how to submit changes after reading this post.
IMHO there should be a submit button.
Maybe the warning message should also have the option to submit changes.
Mick
Alright - first timer to use Database tooling in IntelliJ
It works as following, I can describe it as following
to apply the change i have to do the following ( other wise changes are not really committed to the database )
the issue is that behavior is really confusing. maybe add a submit button ( with commit button enabled only after submit )
it was only because of this post , I was able to get it working.
Documentation and Settings are not clear nor enough too ... it only mentions submit is automatic, which also results in an auto-commit behavior !
Thanks,
/Mo
Same here. This really confused me as well, which is why I ended up here.
What really made me scratch my head:
* edit a value with auto-commit disabled
* submit (ctrl-enter)
* execute a select within IntelliJ --> new value is shown
* execute same select in a different session --> old value is shown (this is where the head scratching happens, since i already 'submitted')
* hit commit
This thread helped me understand how this all works.
Thanks and cheers
I feel like this is a UX bug. Today I tried many time to change a value in an Oracle database using DataGrip with no luck. I would make a change then click the check mark to commit. Then 10 minutes later I would have to debug wth was going on only to find out my change did not commit. I guess I was using it wrong. Ill try again tomorrow with the information I found on this thread. I really hope it works, I don't like using Oracle's SQLDeveloper...