| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
create_date but not an update_date. Fixes the Table Information pane on InnoDB tables and associated draw errors.
|
|
|
|
|
|
|
|
|
| |
preferences - resolves Issue #67;
- Improve field mapping clarity and allow display of duplicate cell values by appending the column number to the current cell value
- Trims blank lines from CSV imports to avoid importing rows filled with defaults
- Correctly encodes linebreaks in CSVs for reimport
|
|
|
|
|
|
|
| |
encoding specific to each table
- Added the selected table's character encoding to the table information pane and removed the table's name
|
| |
|
|
|
|
| |
and evidently decided my version was newer without declaring it a conflict. Fixed.
|
|
|
|
|
|
| |
- Don't output the CSV "headers" for exports of single tables
- Use the correct line ending as specified in the export dialog when exporting CSV headers and spacing for multi-table exports
|
|
|
|
| |
filter field selection changes
|
| |
|
|
|
|
|
|
|
|
| |
properly fixes Issue #110.
- Save favourites on exit - this saves edits such as favourite name changes within the connection sheet which aren't otherwise caught.
- Removes an outdated property (selectedFavourite)
|
|
|
|
| |
to allow filtering for NULLs.
|
| |
|
| |
|
|
|
|
| |
separator that was appearing at the bottom of the 'File' menu.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
result sets - when iterating through a mysql result set, all the data up to each row was seeked through again. With this fixed SP can work with very large result sets at much, much higher speeds.
- Fixed incorrect query splitting in splitQueries - improves custom queries and imports.
- CSV export now exports NULLs as an empty cell (eg "1,,3"). This resolved Issue #67. Correspondingly, CSV import now also accepts this syntax.
- CSV and SQL exports no longer quote numeric values for file size and neatness improvements.
- Multi-table exports now show progress through the tables in the text description, and use the progress bar for export of each table, for improved feedback.
- The old "Export Table Content" menu has been split into two - "Current Browse View" which matches the old behaviour, and a new "Current Table" entry. This addresses Issue #97.
- Exports now write data to a file stream as data is processed for export, and also parse data from the database as a stream where possible. This leads to lower memory usage, speed improvements, and much more accurate and constant feedback.
- The export processes have been restructured and rewritten for further speed and memory improvements.
- SQL exports now correctly export BLOB and TEXT contents ready for re-import into all systems.
- SQL exports now group multiple VALUES for each INSERT INTO command for much, much faster imports of exported data.
|
|
|
|
| |
No longer required to select a table first before selecting the Import... menu item
|
|
|
|
|
|
| |
imports the data into selected table.
Known Issue: a table must be selected in TABLES list before choosing Import... menu.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
---
Field mapping when importing CSV file now makes more sense.
You can import data into multiple columns in the table.
Known Issue: changing table while field mapping doesn't work. Select the table first before importing
TableContent
---
Partially solves issue where label at bottom "x of y rows selected" wasn't being updated
TablesList
---
Moved table delegate methods under correct pragma mark
|
|
|
|
| |
implementation.
|
|
|
|
| |
strings, fixing the data corruption problems in all TEXT/BLOB types
|
| |
|
|
|
|
| |
only applied on enter rather than when the filter string is changed which caused major performance problems on large tables.
|
| |
|
|
|
|
| |
checking if an item of the same name and account already exists. This revision also fixes issue #94 by removing the Keychain password first and then the favourite from the array controller.
|
| |
|
|
|
|
| |
delegate/data source methods as public API.
|
| |
|
|
|
|
| |
make them public as they are called automatically.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
when there is only one value being shown.
|
| |
|
|
|
|
| |
not showing any applied limit on initial table load
|
|
|
|
|
|
|
|
|
|
| |
- Refreshing or reloading a table view will now attempt to preserve sorting and filters.
Other changes:
- Initial cleanup of TableContent loadTable:
- Replacing project-distributed column sort arrows with the OS-provided images
|
| |
|
| |
|
|
|
|
|
|
|
| |
then restore it afterwards - ie suggestion (2) in http://groups.google.com/group/sequel-pro/browse_frm/thread/71541c6267fc08c1/2f4aeeaa7f15b268 .
I was initially in two minds as to whether this would be a good thing, but with r195/r196 removing the need to refresh for structural changes, this change does actually feel right to me - in fact, I now wish it didn't clear any filters/limit, and I'd like to preserve them as well. Any objections?
|
| |
|
|
|
|
| |
changes. Implemented by adding a method to TablesList (setContentRequiresReload) and using it when modifying the tble structure, thus only refreshing if the content is actually viewed again.
|
|
|
|
|
|
|
| |
always thinking I'm on 0.5 and offering me the update. I removed instanced which were the same as the root Info.plist for inheritance.
we should probably consider setting up build variables for the version number and the build number, so localised versions can very easily include those in copyright strings.
|
|
|
|
| |
connectSheet contents into the DBView window. TabView is current tabless with 2 tabs. Main content is in 2nd tab with connectionSheet content in 1st tab.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
favourite whatever the table sort order.
|
| |
|
| |
|
| |
|