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
..
Base/Controller	Merge the BuildResultInfo table into the Builds table	2012-03-12 20:47:29 +01:00
Controller	Don't use a prepared statement for the active build steps query	2012-03-12 20:47:29 +01:00
Helper	Don't use a prepared statement for the active build steps query	2012-03-12 20:47:29 +01:00
Model	* Move everything up one directory.	2009-03-05 13:41:57 +00:00
Schema	Merge the BuildResultInfo table into the Builds table	2012-03-12 20:47:29 +01:00
Script	Use CatalystX::Script::Server::Starman	2011-11-22 16:44:32 +01:00
View	Use the new Nix Perl bindings	2011-11-30 15:25:28 +01:00
Schema.pm	Keep track of the database schema version	2011-12-05 14:29:29 +01:00