Forum Replies Created
-
AuthorPosts
-
Jason O'neilMember'ashwin' wrote:
Hi Jason,
We will fix the filter reset bug in the next public release.
And, We have decided to move data tab, info tab, history tab to the query tab level as they are not dependent on the query tab. This has been added here: http://code.google.com/p/sqlyog/issues/detail?id=1682
We will inform you once we this has been implemented.
Thanks,
Ashwin A
Thanks a LOT! Especially for a non-delay support and feedback!
Jason O'neilMemberI suppose, the simplest solution is
1. Make some “unclosable” tab Global in the second window – if it's active, it has 3 global/OB tabs – History/Info/Table Data.
2. Attach to each Query his “child” tabs (History/Data/Info/Messages/Result) just like it is now.
Jason O'neilMemberI don't insist it's a bug, but is a bit inconvenient with current window composition – if I want to view the History/Info/Table Data – I need to create a Query tab. I'm not even telling that if you close your last Query tab – history will be completely lost.
Those tabs are dependent on Query tab – that's what i mean 'inner'.
Jason O'neilMember'peterlaursen' wrote:Please tell the SQLyog version you are using.
v9.20
Jason O'neilMember'peterlaursen' wrote:I don't get you as regards 4). Could you detail this? Maybe a screenshot with some comments could help?
Some kinda painting
And db dump attached[attachment=1609:dump.zip].
So, in list Neighbor Tables we have all tables listed, which have the same foreign key (book_id) as current table publishing
Jason O'neilMember'vishal.pr' wrote:
@Jason O'neilALT + Selection is used to make rectangular selection and its a Scintilla property, the editor component used in SQLyog. The behavior you mentioned is verified and will be reported to Scintilla developers. If it is confirmed as bug we may provide a fix for this. However, you can try the reverse here. That is, start the selection from top right and extend it to left. this will work.
Regards,
Vishal P.R
Ok, thanks.
Your reverse selection I've tried early, but it does work only if we start/end selection on the longest string. In other words, if we have longest string in the middle of selection – it's cutting selected text.
Jason O'neilMemberAdded 4th feature.
That's a pity about XML/JSON parsers.
-
AuthorPosts