8 messages in com.mysql.lists.eventum-usersRe: Customer logins| From | Sent On | Attachments |
|---|---|---|
| Jeffrey D. Wheelhouse | 12 Mar 2005 18:48 | |
| Joao Prado Maia | 13 Mar 2005 19:17 | |
| Jeffrey D. Wheelhouse | 13 Mar 2005 21:55 | |
| Bryan Alsdorf | 15 Mar 2005 11:46 | |
| Jeffrey D. Wheelhouse | 15 Mar 2005 13:48 | |
| Bryan Alsdorf | 16 Mar 2005 22:03 | |
| Jeffrey D. Wheelhouse | 18 Mar 2005 08:28 | |
| Bryan Alsdorf | 21 Mar 2005 13:32 |
| Subject: | Re: Customer logins |
|---|---|
| From: | Bryan Alsdorf (bry...@mysql.com) |
| Date: | 03/15/2005 11:46:13 AM |
| List: | com.mysql.lists.eventum-users |
Jeff,
Jeffrey D. Wheelhouse wrote:
Joao Prado Maia wrote:
You are supposed to import those users from your existing customer database into Eventum. [...]
Yes, authentication still works against the Eventum user table.
I must still be missing something, because the point of having a customer database is to centralize customer data. But this only works if the entire database of customers is duplicated and then somehow kept in sync (add users, drop users, email changes, password changes)? That seems very anti-RDBMS.
All of the customer data is still in the customer database. The only data that has to be transferred to Eventum is the name and the email address (along with some sort of unique customer ID). Maybe in a perfect world we wouldn't need this, but for now a cron job can solve the problem very easily.
I guess one could do a nasty workaround by telling Eventum to use a view into the "real" customer database instead of its own table for its user info, but MySQL 5.0 is not GA so that's out.
I don't think that would work. When 5.0 is in GA you are welcome to try, but I don't think it will work out that well.
What is the next-best workaround?
I know you don't think this is a proper solution, but having a cron job sync the data works very well. Like I mentioned earlier, it isn't a whole lot of data to keep in sync.
/bryan