| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
resolve all warnings.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
menu to use tag-based values when generating queries, allowing localisation of menu contents without using those localised values in queries. This addresses I$
- Remove the ability to specify a FULLTEXT auto_increment index, as I believe this isn't possible.
- Prevent sheet reuse from specifying invalid storage types for PRIMARY KEYs
- Fix exceptions when adding indexes to a table where every field is already indexed
- Fix initialField/indexedFieldNames check to improve on r3061
- Fix toggling advanced index view after closing the sheet with the view open
- Update localisable strings
|
|
|
|
| |
- fixes issue 886
|
|
|
|
|
|
|
|
|
|
|
| |
central functionality out of SPTablesList:
- Centralise control over table loading, moving it away from SPTablesList and into SPDatabaseDocument and the new SPDatabaseViewController category
- Centralise control over the main tab view, moving control away from SPTablesList and into SPDatabaseDocument and the new SPDatabaseViewController category
- Simplify and clean up view loading logic
- Improve thread safety
- Update localisable strings
|
|
|
|
|
|
| |
auto_increment field now runs doc-modal not app-modal
- the used strategy is to ask the user for an index whenever the user set the Extra field to 'auto_increment' and not as part of the 'addRowToDb' method
|
|
|
|
|
|
| |
Extra only if table has no auto_increment field set since MySQL allows only one auto column
- the user has still the chance to type 'auto_increment' into the Extra manually
|
|
|
|
| |
validation methods to their own class, SPTableFieldValidation.
|
| |
|
|
their own category.
|