Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POchat server: what's the best(optimized) way to save a conversation log
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USkorifey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POchat server: what's the best(optimized) way to save a conversation log
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COthanks for your answer. We're currently using 1.b already and even if we're on beta stage with a closed group of beta testers we have around 30-40 conversations/day and after a month the mysql server is starting to run a little slow. I'm thinking in the future to move the entire database to Apache Cassandra, but for the moment is to much to change and also I need to spend more money on hardware since apache cassandra is resource hungry
      singulars
      1. PO
      1. USDoua Beri
    2. CO@Doua The first thought there shouldn't be "Oh we should really use a NoSQL solution" but more "What in gods name are we doing wrong that a select of a few hundred lines of conversation (you really can't show your users much more at once) of a 400k row table takes so long?". So better go looking whether all the indizes are used correctly (and exist), you only select the data you really need and so on. Much one can do there. Asking a question here with the table schema, the query and an explain wouldn't harm too after you've made sure the obvious things are correct.
      singulars
      1. PO
      1. USVoo
    3. CO@Voo ok. maybe I've wrote a bad example. we achieved 400k rows in 1 months with a minimal numbers of clients(beta testers). once we open the service to public we expect to have 500-1000 or even more clients which will result in a few millions lines/month and probably a few hundred millions after 1 year. The table is very simple. it has 3 columns : conversation_id(int), message(varchar), add_date(datetime), conversation_id and add_date are indexed and the select is something like this: select message from conversation_log where conversation_id=1 order by add_date
      singulars
      1. PO
      1. USDoua Beri
 

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