基于所选值的单个或多个 INSERT
我们正在将网球场的预订信息从 SQL 数据库中提取到一个简单的结果表中,以帮助我们了解球场使用情况。除了持续超过一个小时的预订之外,这非常简单。
目前,每个预订都会在我们的结果表中占据一行。每行包含开始时间、持续时间和法庭编号。我们希望将此表直接映射到电子表格或数据透视表中,以便我们可以了解我们的球场被预订了多少小时以及一天中的哪些时间。
目前,我们的 SQL 查询类似于:
INSERT INTO Results (year, month, day, hour, duration, court)
SELECT DATEPART (yy, b.StartDateTime),
DATEPART (mm, b.StartDateTime),
DATEPART (dd, b.StartDateTime),
DATEPART (hh, b.StartDateTime),
a.Duration,
a.Court
FROM Bookings b
INNER JOIN Activities a
ON b.ActivityID = a.ID
我们的问题是,持续时间为 2、3 或更多小时的预订在结果表中只有一行,即:预订后的第一个小时。这是因为预订的长度是在持续时间数据中捕获的。我们可以对数据进行一些后处理来达到我们的目的,但如果这在我们的 SQL 查询中是可能的,那就更容易了。
是否可以以某种方式修改此查询,以便根据持续时间(可以是 1、2、3、... 小时)将适当数量的行插入到结果表中,每行持续时间为 1。因此 3 - 小时预订从上午 9 点开始,结果表中会出现三行,一行在上午 9 点,一行在上午 10 点,一行在上午 11 点,每行持续时间为 1 小时。
而不是结果表中的以下行
Year, Month, Day, Hour, Duration, Court
2009, 08, 25, 09, 3, 1
因此,我们得到以下行,
Year, Month, Day, Hour, Duration, Court
2009, 08, 25, 09, 1, 1
2009, 08, 25, 10, 1, 1
2009, 08, 25, 11, 1, 1
:这将使将结果表映射到电子表格中更加容易。
更新2009-08-25:当然,正如前几个答案所示,它不一定是单个查询。一套就好了
更新2009-08-26:已经偏离轨道,还没有机会尝试建议的解决方案。希望尽快这样做,并将根据结果选择答案。
2009-08-27 更新:终于有机会尝试解决方案了。整数表和连接产生解决方案令人大开眼界。特别是使用交叉联接来创建这样的表。这可能是更简洁的 SQL 处理方式。
然而,最终我选择了 Aaron 涉及标志和简单算法的解决方案。我确实通过将他的算法包装在 while 循环中以不断迭代直到没有持续时间 > 来增强它。还剩 1 名。这是快速且容易实施的。它还强调我们确实有一些 10 小时的预订,所以我不需要在这里硬编码限制。
我应该注意到,我将 Jeff 的最大持续时间的想法融入到 while 循环计数器中,而不是我最初的想法,即对持续时间 > 的项目进行计数。 1.代码稍少。
We're extracting booking information for our tennis courts from our SQL database into a simple results table to help us build a picture of court usage. It's pretty straight-forward except when it comes to bookings that last more than an hour.
At present, each booking results in a row in our results table. Each row contains a start-time, duration and court number. We'd like to map this table directly into a spreadsheet or pivot table so we can see how many hours our courts are booked and which hours of the day.
Currently, our SQL query looks something like:
INSERT INTO Results (year, month, day, hour, duration, court)
SELECT DATEPART (yy, b.StartDateTime),
DATEPART (mm, b.StartDateTime),
DATEPART (dd, b.StartDateTime),
DATEPART (hh, b.StartDateTime),
a.Duration,
a.Court
FROM Bookings b
INNER JOIN Activities a
ON b.ActivityID = a.ID
Our problem is that bookings for 2, 3 or more hours duration only have one row in the results table, ie. for the first hour of the booking. This is because the length of the booking is captured in the duration data. We could do some post-processing on the data to achieve our ends, but it would be easier if this was possible in our SQL query.
Can this query be modified in some way, such that depending on the duration (which can be 1, 2, 3, ... hours) the appropriate number of rows are inserted into the results table, each of duration 1. Thus a 3-hour booking starting at 9am, would results in three rows in the results table, one at 9am, one at 10am and one at 11am, each of duration 1-hour.
So instead of the following row in the results table:
Year, Month, Day, Hour, Duration, Court
2009, 08, 25, 09, 3, 1
we get the following rows:
Year, Month, Day, Hour, Duration, Court
2009, 08, 25, 09, 1, 1
2009, 08, 25, 10, 1, 1
2009, 08, 25, 11, 1, 1
This would make mapping the results table into a spreadsheet much easier.
UPDATE 2009-08-25: Of course, as the first couple of answers show, it doesn't have to be a single query. A set is fine.
UPDATE 2009-08-26: Have been side-tracked and haven't had a chance to try out the proposed solutions yet. Hope to do so soon and will select an answer based on the results.
UPDATE 2009-08-27: Finally got a chance to try out the solutions. The table of integers and joining to produce a solution was an eye-opener. Especially the use of cross-joins to create such a table. This is probably the cleaner, SQL way of doing things.
However, in the end, I went with Aaron's solution involving the flag and the simple algorithm. I did enhance it by wrapping his algorithm in a while loop to keep iterating until no durations > 1 were left. This was quick and easy to implement. It also highlighted that we did have some 10 hour bookings, so I didn't need to hard-code a limit here.
I should note that I incorporated Jeff's idea of max duration into the while loop counter, rather than my original idea of count the items with duration > 1. Slightly less code.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(5)
编辑以更正缺失的小时计算
创建一个单列临时表,其中包含 n 行整数 n -(我假设最大预订时间为8小时)。
您可以使用以下查询验证临时表是否具有正确的行数:
修改您的查询以包含临时表的联接:
编辑 - 说明其工作原理
当联接表时, row 是在源表中满足连接条件的连接行的每个组合的输出中生成的。
我使用临时表将预订和活动的原始结果集“乘以”预订持续的小时数(通过加入持续时间)。仅当预订是在整数小时内进行时才有效。
如果您想更清楚地看到这一点,请向 #t 添加第二列,该列唯一标识每一行并将其包含在输出结果集中:
这应该澄清结果集中的每一行都是由 Bookings 的单个有效组合生成的,活动和#t。
Edited to correct the missing hour calculation
Create a single column temporary table with n rows for integer n - (I've assumed that the maximum booking time is 8 hours).
You can validate that the temporary table has the correct number of rows with the following query:
Amend your query to include a join to the temporary table:
EDIT - a clarification on how this works
When joining tables, a row is produced in the output for each combination of joined rows in the source tables which meet the join criteria.
I'm using the temporary table to "multiply" the original result set from Bookings and Activities by the number of hours that the booking lasts by joining on Duration. This only works if bookings are made in whole numbers of hours.
If you want to see this more clearly, add a second column to #t which uniquely identifies each row and include it in the output result set:
This should clarify that each row in the result set is produced from a single valid combination of Bookings, Activities and #t.
如果您引入 整数,则对原始内容稍加修改就足够了 表(或
VIEW
)用作系列生成器:A slight modification to your original suffices, if you introduce an integers table (or
VIEW
) to serve as a series generator:这不是小事。首先,您需要另一列“Flag”,其值为 0:
您需要多次运行这些查询:
这将为每个
duration > 创建一个附加条目。 1.
.我的猜测是,你不能分配一个超过 8 小时的球场,所以你只需要运行这三个 8 次即可修复所有问题。It's not trivial. First, you need another column "Flag" which is 0:
You need to run these queries several times:
This will create an additional entry for each
duration > 1
. My guess is that you can't allocate a court for more than 8 hours, so you just need to run these three 8 times to fix all of them.您可以考虑在表“结果”上放置一个 INSTEAD OF INSERT 触发器,该触发器将为每个超过一小时的预订插入多行。这确实增加了复杂性,但它可能是一种合理的方法,因为这听起来不像是大容量 OLTP 系统。
You might consider putting an INSTEAD OF INSERT trigger on the table "Results" that would insert multiple rows for each more-than-one-hour booking. This does add complexity, but it might be a reasonable approach, since this doesn't sound like a high-volume OLTP system.
我还没有机会对此进行调试,但是类似这样的事情应该可以为您完成:
I haven't had a chance to debug this, but something like this should do it for you: