The alternative for me is to have the results contain a field that describes what I'm looking at (so making the beginning of the query SELECT 'YEARLY') for example. It's hardly a deal-breaker, but it would make it much simpler to read the results. Being able to label the tabs in a multi-query is just another small feature that I'd love to have. Heidi is an excellent tool that I've been using for donkeys, but there's no single feature that makes it a killer app, but rather a collection of MANY small features that just makes it indispensable, IMHO. It certainly won't require massive documentation, will it? Also, why would I want to write an application or framework to get data out, when Heidi already does it brilliantly? Quickly knock up a query, export data as CSV (or whatever is required), save the SQL file for later use, done. Adding a tiny little bit of processing such as this also doesn't add any complexity to the application, if you're perfectly honest. OK, firstly, the age of the thread does not change the fact that this is a feature that I've wanted for a while. ġ0 Feb - ansgar: Get message 'you have no privilege. ġ3 Feb - Calm_Temperature1211: Downloading older Heidi ve. ġ3 Feb - MaWi: Bestehende Datenbank mit HeidiSQL Kopieren. ġ3 Feb - berbo: HeidSQL UI not opening - It's runnin. ġ3 Feb - Jorg71: Query is not updated after adding a colu. Ģ4 Feb - BerLech: Next Data field edit with Tab keyġ9 Feb - ansgar: Autimatic Backup at any DAYġ6 Feb - ansgar: SQL Error: can't connect to MySQL s. Ģ6 Feb - jaume: Format 'Fitxer de configuració port. Ģ7 Feb - iksi: Question regarding dialog for connecting u. Requirements Enabled query, and collect performance schema statistics. Ģ8 Feb - yonisade: BUG: Unhandled Exception when Export D. Query Statistics in MySQL - The important statistics collected for a performed query, including time, temporary tables, indexes, joins, and more, are gathered in the Query Stats SQL editor results tab (see the following two figures). Ģ8 Feb - LakiGeri: Request / suggestion: autogenerate tab. Ġ1 Mar - ansgar: Altering table engine ARIA => InnoDB. You may want toĠ3 Mar - tihoho: Filter for display columnsĠ3 Mar - ronek99: Autocomplete size is too smallĠ2 Mar - JenniferMorgan: Adding default value for a bit c. User support and hosting takes time and money. But keep in mind that developing HeidiSQL,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |