The only situation where the user table would be deleted given a standard login/user engine setup would be if *you* ran:
rake engine_migrate ENGINE=login_engine VERSION=0 ... which is a pretty specific command. Because of this I'd say that it's quite safe to place your extra data in the user table where it almost certainly belongs. There are probably many simpler and more likely ways to trash your database than this. - james On 2/4/06, Jay Levitt <[EMAIL PROTECTED]> wrote: > I'm just starting with the UserEngine on a new app. I'm going to have a > bunch of other per-user data: phone number, AIM name, etc. Would it be > better to add these as fields to the Users table, or to say that User > :has_one Profile, and put them in @user.profile? I've seen some people > have trouble with has_one syntax but I haven't tried either way myself yet. > > Any advantages/disadvantages to either approach? After noticing that the > UserEngine down-migration deletes Users, I feel uncomfortable trusting it > to leave my fields alone, but conceptually, these fields do belong to User. > > Jay Levitt > > _______________________________________________ > engine-users mailing list > [email protected] > http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org > -- * J * ~ _______________________________________________ engine-users mailing list [email protected] http://lists.rails-engines.org/listinfo.cgi/engine-users-rails-engines.org
