silverstripe-framework/tests/forms/ComplexTableFieldTest.yml

ComplexTableFieldTest_Player:
   p1:
      Name: Joe Bloggs
   p2:
      Name: Some Guy
ComplexTableFieldTest_Team:
   t1:
      Name: The Awesome People
      Players: =>ComplexTableFieldTest_Player.p1,=>ComplexTableFieldTest_Player.p2
   t2:
      Name: Incredible Four
ComplexTableFieldTest_Sponsor:
   s1:
      Name: Coca Cola
   s2:
      Name: Pepsi
Merged from branches/2.3 git-svn-id: svn://svn.silverstripe.com/silverstripe/open/modules/sapphire/trunk@75845 467b73ca-7a2a-4603-9d3b-597d59a354a9 2009-05-01 05:49:34 +02:00			`ComplexTableFieldTest_Player:`
			`p1:`
			`Name: Joe Bloggs`
			`p2:`
			`Name: Some Guy`
			`ComplexTableFieldTest_Team:`
			`t1:`
			`Name: The Awesome People`
ENHANCEMENT: Refactored TableListField and subclasses to rely on the DataList to handle data manipulatation. API CHANGE: A DataList can be passed as the 2nd argument to the constructor; this is the recommended approach for editing non-relations. API CHANGE: You can't set a custom query; only a custom DataList. API CHANGE: You can't have one of these fields editing data that doesn't correspond to a DataList - there must be some kind of DataObject behind it. API CHANGE: If the field's name corresponds to a relation on the object being edited, then the relation is used as the data set - all the source* parameters are ignored. API CHANGE: relationAutoSetting only works if your form has had the corresponding data object loaded with $form->loadDataFrom(). API CHANGE: relationAutoSetting can't be turned off; attach a non-relation DataList instead. 2009-11-22 07:07:45 +01:00			`Players: =>ComplexTableFieldTest_Player.p1,=>ComplexTableFieldTest_Player.p2`
Merged from branches/2.3 git-svn-id: svn://svn.silverstripe.com/silverstripe/open/modules/sapphire/trunk@75845 467b73ca-7a2a-4603-9d3b-597d59a354a9 2009-05-01 05:49:34 +02:00			`t2:`
			`Name: Incredible Four`
			`ComplexTableFieldTest_Sponsor:`
			`s1:`
			`Name: Coca Cola`
			`s2:`
			`Name: Pepsi`