By hortitude on

I am developing a site that is saving non visible user data upon login (e.g. external ID on another site). We are going to create/save this data as soon as the account is created.

I could see us saving data using

1) the content profile module (already in use on our side)
2) the profile module
3) the data column in the user table
4) creating our own table

I feel like #1 is probably the most logical place, however creating a node within a module does not seem to be a trivial thing.
#3 feels like a typical way to solve this, but just having a bunch of serialized data in a catchall field does not feel like the best design.

Any suggestions?

⋅ Categories: Drupal 6.x

Comments

cayenne’s picture

cayenne commented

I have exactly the same need. Used CCK to make a content type that acts as a link between user and the external ID.
I am considering changing this to being a hidden profile field.

If you would like my custom module that deals with this, drop me an email. It's rough, but workable

:)

pedrorocha’s picture

pedrorocha commented

I have the same need and solved with Profile module, without problems. Seens the best way for me, for two reasons:

* Core module
* Less and cleaner code to use

But if you are already using CCK, maybe will be good to use it and do not load another module(Profile) just for 1 field.
I don't know the exactly cost of this, but 1 more module is always 1 more module to be called in every request.