Skip to content

Commit

Permalink
Added section about migrating from DOM issue 16
Browse files Browse the repository at this point in the history
  • Loading branch information
UndefinedOffset committed Nov 22, 2012
1 parent a6a73c2 commit 25c1809
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,5 +31,13 @@ $myGridConfig->addComponent(new GridFieldSortableRows('{Column to store sort}'))

To move an item to another page drag the row over the respective page button and release.

## Migrating from SilverStripe 2.4 and Data Object Manager's SortableDataObject
SortableGridField is not the same as SortableDataObject, since it is only a component of GridField it does not have the ability to catch the object when it is saved for the first time. So SortableGridField uses 1 as the first sort index because 0 is the default for an integer field/column in the database. For migrations from 2.4 with SortableDataObject you need to setup your DataObject based on the instructions above however you must name your sort column "SortOrder" to maintain your sort indexes defined by SortableDataObject. Then you need to run the following query on the table containing your sort field, for many_many relationships this will be something like {RelationshipClass}_{RelationshipName}. This query will maintain your sort order from SortableDataObject but increment the index by 1 giving it a starting number of 1.

```sql
UPDATE YourTable SET SortOrder=SortOrder+1;
```


## @TODO
* Optimize re-ordering of a has_many relationship when sorting on a single page

0 comments on commit 25c1809

Please sign in to comment.