Eelco Dolstra 8d65ab6158 Don't use a prepared statement for the active build steps query
Prepared statements are sometimes much slower than unprepared
statements, because the planner doesn't have access to the query
parameters.  This is the case for the active build steps query (in
/status), where a prepared statement is three orders of magnitude
slower.  So disable the use of prepared statements in this case.

(Since the query parameters are constant here, it would be nicer if we
could tell DBIx::Class to prepare a statement with those parameters
fixed.  But I don't know an easy way to do so.)
2012-03-12 20:47:29 +01:00
2011-11-22 14:56:37 +01:00
2010-09-30 14:29:15 +00:00
2011-01-14 10:52:47 +00:00
2011-11-30 18:14:48 +01:00
2010-03-29 14:16:46 +00:00
2010-09-30 14:29:15 +00:00
2011-03-16 09:07:55 +00:00
2010-09-30 14:29:15 +00:00
2010-09-30 14:29:15 +00:00
2011-12-05 15:53:23 +01:00

The file is empty.
Description
No description provided
Readme 18 MiB
Languages
Perl 70.5%
C++ 15.5%
Nix 6%
PLpgSQL 3%
Shell 2.3%
Other 2.6%