3 ms·
Is there a recommended design pattern to deal with the problem of coalescing or "stringing together" multiple "phantom profiles" inadvertently created for a use
by cpeterso 15y ago
Is there a recommended design pattern to deal with the problem of coalescing or "stringing together" multiple "phantom profiles" inadvertently created for a user every time they browse when logged out (or from different machines before logging in)? I imagine the site's database schema would require one or two extra levels of indirection to map user IDs to user histories.