Tag Info

New answers tagged

0

EXPLAIN the SELECT subquery. (This will workaround the point that jynus brought up.) Your KEY vigi_unique can be made somewhat better by adding id onto the end of it. This will change the EXPLAIN to say "Using index" because it will be a "covering index". But the real reason for 5.6 to be faster is ... The subquery is after "LEFT JOIN", so 5.5 ...


0

I think the answer depends upon how your app is intended to work. Do you envisage users being able to reply to many messages? Or only to a single message? Personally id keep all messages in a single table with a self join. (Like a employee heirachy where each employee has a manager). To speed up searching and selection you could keep all related replies ...


0

I would suggest against using a serialized array, but instead encourage you to build the functionality into your database so that it can be more easily expanded and managed. Given that you're considering implementing a serialized array, I assume that messages can be a reply to zero or more other messages. In this case, a linking table for replies would be ...


0

Your question is not very clear on this point but I'm assuming you want to find overlaps with a proposed, new booking. Let the values for the proposed booking be held in the variables @StartDate, @EndDate and @RoomID. The SQL will be select RoomID, StartDate, EndDate from TheBookingTable as t where t.RoomID = @RoomID and T.StartDate <= ...


1

One of my favorite approaches to problems like these in the context of data warehousing usually takes the form of an agile design practice, where the granularity of a system does not need to always be "rolled up" from the lowest level right away, but can be, as stated in the title of the topic "drilled down" into, as the finer granularity details become ...


0

Elasticsearch is nice to use, any solution will have unneeded features. But why not this for a persistent key value storage solution http://rocksdb.org/


1

For your use case of key-value data, where the value is simple, MongoDB is more than you need. It is a document-oriented data store for complex value types. A specific key-value store would suit your needs. RIAK is the one I've looked at though several others exist. Since your retrieval will be by time range i.e. key range, Elastic's full-text ...



Top 50 recent answers are included