vertical forms

This has been suggested before but using \G in the command line tool for vertical forms is awkward, klutzy. Might as well use workbench even though it has its own issues. Heidi is so much better and vertical forms would be most welcome especially with options to set row height and width.

In searching the forum for this feature a reply to this feature request seemed strange, even patronizing. It suggested that tables with a large number of columns (the original poster mentioned 20+) was bad design and that tables should be smaller. In my view this is nonsensical. Application determines design and breaking up tables results in multiple joins thereby increasing query complexity and the chance of runtime errors and also defeating the suggestion. I'm curious what other forum users think.

I think this is what issue #116 requests, so you're not alone here.

Advices to "fix" a table design by reducing columns are irrelevant. Table design is not done for grid editing but for application logic.

I figured.

If I may I'd like to make two suggestions: when editing table rows tabbing to the next column should automatically select that column instead of requiring a mouse click or the Enter key to put the column contents in edit mode. In other words once edit mode is set for one column it should continue for all other columns as long as Tab/Shift Tab is used. This logic should probably persist in queries with key columns although editing a key might pose difficulties. It could be an option in Preferences.

When a row is selected by clicking on its row number Copy (Ctrl-C) should copy the entire row not the selected column only. Again, it could be an option.

Do you see a pattern? I like options and use them liberally in my work.

I love what you've done here. Heidi is a truly awesome project. Hats off...