romanb 78f5a2edcb More refactorings. Commented out the plugin tests for now. They seem to wreak havoc with a lot of other tests (especially validator tests) and i havent found the reason yet.		2007-11-24 18:11:09 +00:00
..
Association	Lots of formatting changes, cleanup, doc block changes.	2007-10-03 21:43:22 +00:00
Parser	Lots of formatting changes, cleanup, doc block changes.	2007-10-03 21:43:22 +00:00
Association.php	More refactorings. Commented out the plugin tests for now. They seem to wreak havoc with a lot of other tests (especially validator tests) and i havent found the reason yet.	2007-11-24 18:11:09 +00:00
Exception.php	Lots of formatting changes, cleanup, doc block changes.	2007-10-03 21:43:22 +00:00
ForeignKey.php	Mass search and replace for coding standards changes, doc block formatting, and code spacing.	2007-10-21 06:23:59 +00:00
LocalKey.php	Mass search and replace for coding standards changes, doc block formatting, and code spacing.	2007-10-21 06:23:59 +00:00
Nest.php	Mass search and replace for coding standards changes, doc block formatting, and code spacing.	2007-10-21 06:23:59 +00:00
Parser.php	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