Ticket #1 (enhancement)

Opened 5 months ago

Last modified 5 months ago

Split sg_guard_user custom columns into a profile table

Status: new

Reported by: nperriault Assigned to: jtexier
Priority: major Keywords:
Cc:

The sf_guard_user have too much custom columns, there should be a sf_guard_profile table to store them.

Also, when the column split job is done, make a script to migrate the actual data into the new modified schema (we can use the bundled sfPropelMigrationLightPlugin.)

Change History

03/30/08 23:07:55: Modified by jtexier

Moving profile data now present in sf_guard_user (extended by sfPropelAlternativeSchemaPlugin) to a dedicated profile table is quite tricky considering interactions with sfLucenePlugin and sfPropelActAsLocalizableBehaviorPlugin.

What has been done :

  • added a new user_profile table on the schema.
  • moved most of the needed method from PluginsfGuardUser? to UserProfile? and write mappings on PluginsfGuardUser? to avoid breaks on templates (ex: $sf_guard_user->getDisplayName() still works)
  • added batch/convert_user_profile.php to copy existing data on user_profile
  • updated data/fixtures/data.yml
  • validated changes by running test/unit/Karma (slightly updated to test new profile)

What remains :

  • really test that's ok