Hey all,
Going to introduce a second DB shortly, for a specific feature. Current constructing the schema and wondering how/where most here who use two db’s might store their user credentials. Do you have credentials for access on both separate DB’s? Or just one on the main DB?
Unless there’s a specific reason for it, I keep credentials in the main DB (or API if I’m using a third-party security provider). It just means filtering from two database connections on some server action steps which is easier now with the new Globals feature.
Thanks @max_gb - I was thinking as much, seemed overkill to have two set of user credentials. The new DB is there for data storage on a new feature, so I’ll just use globals (when they introduce globally accessible values this Thursday!)
I generally work to a rule of “don’t store any data twice” because it can only lead to possible sync issues down the line. And you’re just giving yourself twice as much work. I would have thought the records in the second DB can just link to the first DB via a record id field.
I was thinking of having a basic ‘user’ table, without credentials that I can then match all SC’s against the session securityID, but that was as far as I was going to take any duplicate data. Do you advise against that approach?
Yep, that sounds spot on to me.
thanks @sitestreet 