StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14637959
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-02-01T00:55:36.617
FavoriteCount
0
LastActivityDate
2013-02-01T00:55:36.617
LastEditDate
LastEditorUserId
0
OwnerUserId
812837
ParentId
14636614
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
This is actually a fairly sane setup to query. Personally, I'd recommend following @inhan's advice, especially if it turns out cars can be booked for smaller slices of time (hours?). However, the queries get a little bit more complicated to write, because of edge-cases (if you look around here, you should find relevant examples). Unfortunately, I can't speak to how this fits into your framework, but the SQL can look like this: <pre><code>SELECT Cars.car_id, Cars.name, Cars.description FROM Cars JOIN (SELECT car_id FROM Cars_Availability WHERE `date` >= '2013-02-05' AND `date` < '2013-02-09' AND status = 1 GROUP BY car_id HAVING COUNT(*) = DATEDIFF('2013-02-09', '2013-02-05')) Available ON Available.car_id = Cars.car_id </code></pre> (Have an <a href="http://sqlfiddle.com/#!2/5f970/2" rel="nofollow">SQL Fiddle Example</a>) This query assumes that there's only one entry per day, or this breaks. Basically, it grabs every 'available' row greater-than/equal the beginning date, and less than the 'end' date (date/time/timestamps are... complicated; <a href="http://sqlblog.com/blogs/aaron_bertrand/archive/2011/10/19/what-do-between-and-the-devil-have-in-common.aspx" rel="nofollow">this article</a> deals with SQL Server-specific problems, but the basic concepts apply), and makes sure there's one for the count of days between them. Mostly, you were looking for the <code>HAVING</code> clause. Given the proper index on <code>Cars_Availability</code>, it may not even hit the table, making this a good performer, too.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POQuerying available rental dates for a vehicle
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USClockwork-Muse
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POQuerying available rental dates for a vehicle
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COWow! Thanks a lot, this seems to be exactly the thing I'm looking for. Cars will never be bookable for less then a day so this won't break.
 singulars
 PostPostId
 PO
 UserUserId
 USIvar

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.