Databases
StackOverflow2013
Postsdbo
POBest way to store and handle usage 'profiling' information?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBest way to store and handle usage 'profiling' information?
    primarykey
    data
    text
    <p>I'm sure there's an easy answer here and i'm just over-complicating things, but i am in the process of writing a Django module responsible for storing and tracking user usage statistics which can then be displayed to users on certain pages.</p> <p>Simplest example of this might be tracking which products a user has purchased and looked at so that when someone else is looking at a product we can display "products other people bought that also bought this"... etc</p> <p>My uncertainty is to do with the best data model approach. I am thinking that it might not be efficient to write to a table every time someone looks at a product, but then i do need to display this data in some form to users. I'm looking for a strategy that is easy to manage and that is efficient from the bottom up. Any suggestions?</p> <p>EDIT: By 'efficient from the bottom up' - i'm basically just talking about adopting a solution that is efficient to both store and retrieve - probably should have just said that :)</p> <p>Also, to add another complication, let's say i want to track viewing relationships between products rather than simply logging that an individual product was viewed. So, for example i might want to show on product A's page that people who viewed product A also viewed product b c and d. On the back of some of the comments below i was thinking about creating a table / django model with 2 simple fields (product_name and last_viewed_date), that way i can run a job to consolidate all views of a single product into one row (with the last_viewed_date taking the date of the most recent record)... BUT if i also want to store the history of each of those views, as explained above, how might i do that?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBenjamin Dell
    1. USBenjamin Dell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBest way to store and handle usage 'profiling' information?
      1. UStourist
      1. VTFavorite
    1. COcan you explain what you mean by "efficient from the bottom up"
      singulars
      1. POBest way to store and handle usage 'profiling' information?
      1. USRaj More
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload