Time Granularity

It partially depends on how Date is storing dates for when the date granularity is "Day". Do we know for sure it's using midnight?

The module is built so that, like a calendar, events overlapping on a minute don't block availability. Day-bookings break that assumption, as the end date should be blocked.

I think the best solution is to have it check the granularity setting of the field, and if it's set to "day" (or month / year?) use a different algorithm.

I'm new to drupal so I'm trying to figure out how I can check the granularity set for the datetime field for the content type. If it is set to "day" then I think changing the query to:

      $query = "SELECT DISTINCT nid FROM $date_table
      WHERE('%s' >= $start_field_name AND '%s' <= $end_field_name)
      OR('%s' >= $start_field_name AND '%s' <= $end_field_name)
      OR('%s' <= $start_field_name AND '%s' >= $end_field_name)";

Where I have changed

      WHERE('%s' > $start_field_name AND '%s' < $end_field_name)

to

      WHERE('%s' >= $start_field_name AND '%s' <= $end_field_name)

appears to work so that if there exists an event from

17-Feb to 19-Feb

Then events from
15-Feb to 17-Feb
and
19-Feb to 23-Feb

will cause a conflict.

You should be able to get the field information by calling content_fields($date_field). Install the devel module and dpr() the return of that function to check. Then you should be able to wrap an if around $query to set it properly.

@garg: I'm new too, where can I find this query?

:-/