Hi.
MariaDB, in a 'view' editor mode, when type a select query, when enter a 'space' keep hang. Especially when right after 'AS'(alias)
Hi.
MariaDB, in a 'view' editor mode, when type a select query, when enter a 'space' keep hang. Especially when right after 'AS'(alias)
Isn't that the same issue which you posted here?
Erm, I do not know what you 'QuotedDatabase' mention. there is some of different types of crashs which Im keep sending it. So..i do not know which one is which.
btw, I have put a reproduce steps in one of latest crash report. Please check the one of latest one.
There was no connection broken.
I guess you mean this one?
Right after 'Save' a edited view
> goto [DATA] tab to check.
it occur.
really frequent.
I did exactly that (edited a view and clicked the data tab), but I get no crash. So this probably depends on the view or the underlying table. Could you post the create definition of the view and the table(s) behind the view?
Erm....the view combination of views and each views also reference another view as hierarchy. if look at the very bottom of the view, there is tables which multiple join. which means, I assume, each columns use implicit type internally. (And....the contents bit sensitive.. so cannot show you the contents.)
Column counts are seem that over 90? 80? 100? or so. And the last view contain math fuctions multiple(exp, log, if, ifnull that are calc purpose on some nested sub queries).
FYI, the status log at the screen below. When the crash occur(mean that after edit view and save until click [Data] tab) the '/ Ping server ... /' not displayed but right after CRASH multiple '/ Ping server ... /' log appear suddenly.
when click [save] something affect to the connection since the [save] calls lots of information load from the server (column information and so on.)
Just talking.
Silence two crashes in QuotedDatabase and IsSameAs. See https://www.heidisql.com/forum.php?t=39040
As said the only helpful thing would be a reproduction recipe, probably with the right tables/views. Anyway, I just silenced two crashes which were reported several times, new build will appear in a few minutes. The one crash you reported the last times is one of them. I cannot reproduce both of them, but in the end these are harmless issues, so silencing should not create new problems.
one reprostep from myside is,
there is long query
in the middle of query that sub query as below. select
at the end of the word 'match_key' of above query(means middle of the entire query)
press enter > press back space > type 'order' > and press space then hang.
Just talk that I'm keep watching the symptom whether possible to reproduce, and will keep you post it.
BTW, it must be memory overrun or equivalent error that 200% sure. In this morning Ive got the error under quite controlled situation only with 3 lines(about..less 100 chars) but I only produce the hang error only twice, but now any more... Please look at the Highlight editor in detail.
What today verified is the symptom is that
it occur when the editor try to change lower case to upper case for keywords. For example, middle of 400~500 lines of query, editing subqeury, and type 'where' (small case) and enter 'Space' to expect be upper case. In that case hang. I think 'order' also same situation as report above.
And.. why don't you try to write queries yourself to fix the sypmtom. We cannot help you to pick a 100% reproducible steps. since these are not specific error. only way is, you do write long query, and edit, adjust middle or random as you want.
Hey, that was what I did all the time. Only it did not hang here as on your side. That's why I was asking for a reproduction recipe.
Just did that again, with a 600 line query tab, writing keywords which are uppercase'd after a space. Again I get no issue here.
Did you remove Unicode/Korean characters testwise?
If I remember correctly, some of error happened on pure query. (reason why I told you that multibyte charactor is some of old source handle string as MBCS, not unicode which make memory crash, that was why to give a hint. Now a days, most of source must not handle string as MBCS.)
... and...another idea you give it a try is that, would check the error POSSIBLY occur well in the VIEW edit mode,(not any query edit mode but the VIEW edit mode, you know what im saying. that loaded from the db directly and save) which connected to the buttons UI handling when typing and status change of edit widget. it possibly UI error may not editor error. Hope that u understand what I meant. (one of hang symptom I saw today was, crash detector poped up, and I press report, but hang forever. so didn't send you the report)
Hi. any progress on this?
Now only can use turning off auto-completion as you requested. No intellisense and any support feature at all. (it dramatically reduce hang and errors. but still unknown quiting withut any of notice. just disappearing.)
Seem that there are some of untrackerable errors vary. You should fix the this editor crash matter that windows hooking mechanism, then you will get free from the big errors.
Please login to leave a reply, or register at first.