when used in a setup task. The output created didn't add a line ending.

Returns true if the instance was registered with IoC::instance

Signed-off-by: aeberhardo <aeberhard@gmx.ch>

global, to allow aliases to work, and allow class extending.

get_dirty() must compare using Not Identical (!==) on place of Not Equal (!=).
For example, changing null to false don't make the model dirty.

Most SLL-related code in Laravel checks to see if `application.ssl`
is true before doing an action requiring it. `Cookie::put()` is the
only exception that I've found, to date, that doesn't test for SSL.

This checks to see that the SSL is enabled when attempting to set a
secure cookie.

To verify, set `application.ssl` to false (without this patch) then
run:

	Cookie::put('foo', 'bar', 0, '/', null, true);

You will get an exception because of line 90 in `cookie.php`:

		if ($secure and ! Request::secure())
		{
			throw new \Exception("Attempting to set secure cookie over HTTP.");
		}

With this patch you will not get this error unless both `application.ssl`
is true, and the cookie `$secure` flag is set.

Signed-off-by: Steven Klar <steven.klar@mayflower.de>

Signed-off-by: bruston <benjy.ruston@gmail.com>

Sometimes the logged queries would be rendered with visible
HTML entities in the profiler, due to double encoding (You know,
> stuff). I could not find out why it was being escaped
twice, but I found an easy fix: since PHP 5.2.3 the htmlspecialchars
function had a double_encoding parameter that could be set
to false. Voilà!

Self-explanatory.

When running nginx with php-cgi (Fast-CGI): 

spawn-fcgi -a 127.0.0.1 -p 10081 -C 50 -u nobody -f /usr/local/php5317/bin/php-cgi

The Request::cli() method will determine the web request as run from the command line.
Add ` PHP_SAPI != "cgi-fcgi" ` to resolve it.

If password is set in the config (database.php), before to issue any command it starts the Auth process, otherwise it starts with SELECT as usuale.

When query time is larger than one second 'array_sum' cannot convert it
to float right. Also, it is better to fire 'laravel.query' event with
raw time as an argument rather than its string representation