1
0
mirror of synced 2024-12-14 07:06:04 +03:00
Commit Graph

9 Commits

Author SHA1 Message Date
romanb
cfc7d4e423 Refactoring. Started to introduced a clear separation between column names and field names (aka column aliases).\nDoctrine_Connection, DQL Parser classes/methods map field names => column names.\nDoctrine_Hydrate maps column names => field names during hydration.\nColumn names are only stored in Doctrine_Table:: and Doctrine_Table::.\nRelations use column names in 'local'/'foreign'.\nWhen using field names (column aliases) you need to use the column names in 'local'/'foreign' when setting up a relation (hasOne/hasMany), not the field names.\n\n In other words column names are only used to communicate with the database. field names are used everywhere else. the casing of field names does not matter. column names are forced to lower case for portability. If you dont use field names (column aliases) your column names are your field names (and therefore all lowercase). 2007-11-18 16:06:37 +00:00
zYne
2e5dd84fc2 tests for CTI column referencing in DQL 2007-11-15 13:45:41 +00:00
zYne
ad42e81ff3 tests for abstract base class in CTI inheritance tree 2007-11-10 13:23:02 +00:00
zYne
c6a0dd655b tests for deleting CTI records 2007-11-10 13:09:14 +00:00
zYne
199dbbc23f more tests for the class table inheritance 2007-11-10 01:01:23 +00:00
zYne
11ee8e33bb tests for basic CTI fetching 2007-11-09 13:23:39 +00:00
zYne
d1c23818f9 tests for inserting CTI record instances 2007-11-08 22:56:03 +00:00
zYne
c6e99ade91 tests for CTI exporting 2007-11-08 22:15:37 +00:00
zYne
af4f85ae69 some tests for class table inheritance 2007-11-07 23:00:24 +00:00