rails.git - Mirror of official rails repo with custom fixes.

	Commit message (Collapse)	Author	Age	Files	Lines
*	postgresql visitor is working	Aaron Patterson	2014-04-08	1	-10/+11
\|
*	Add Regexp and NotRegexp nodes for PostgreSQL	James Le Cuirot	2014-04-08	1	-0/+8
\|
*	Removed all the fiels in lib/arel/visitors/ which needs dependency on 'a' ↵	Alex Lin	2014-03-24	1	-8/+6
\| \| \| \|	also fixed the test case for : test/visitors/test_to_sql.rb:22 which pass in the parameter attribute e.g the parameter a.
*	PostgreSQL bugfix for invalid SQL in subqueries	vanderhoorn	2014-02-05	1	-0/+2
\| \| \| \| \| \| \|	In commit 68a95542e1a7a79d9777223fbffd2b982fed0268 the last_column feature of ToSql was removed. The visit_Arel_Nodes_Matches and visit_Arel_Nodes_DoesNotMatch methods are overwritten in the PostgreSQL class, but were not updated appropriately. This commit fixes the issue accordingly. This bug affects at least all update_all statements in Rails 4.0.2 that have subqueries with ILIKE statements on PostgreSQL. The bug is present in Arel 4.0.1 and later, so it probably affects most Rails 4.0.2 projects. It would be highly appreciated if Arel 4 could get a point release as well. Thanks for your continued work.
*	Make visitors threadsafe by removing @last_column	Ernie Miller	2013-04-28	1	-6/+6
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The last_column feature of the ToSql visitor and its descendants is what enabled quoting based on the column last visited -- in other words, if you have a standard condition like an equality with a string attribute on the left side and an integer on the right side, then when ARel visits the node, it'll first visit the left side attribute, setting the column of the string attribute as the last column, and resulting in the right side of the condition getting the appropriate quoting. The downside is that this means that visitors can't be shared between threads, because of the state mutation. It also makes for some really weird behavior in the event that the visitor visits a node that happens to contain an attribute you weren't expecting to be there, since it'll potentially quote something based on that attribute. So, it prevents reversing an equality condition. column = value will work, but not value = column, since the last column wouldn't be the column you're hoping for. This is a first pass at fixing this by changing the signature of the visit methods to accept the currently-relevant attribute, if any.
*	Support locking by default and disable it only for SQLite.	Edgars Beigarts	2011-08-26	1	-3/+0
\|
*	removing the aliased orders method from the pg visitor	Aaron Patterson	2011-04-28	1	-13/+0
\|
*	adding Distinct ON node	Aaron Patterson	2011-04-21	1	-25/+2
\|
*	refactoring custom lock logic to use sql literals	Aaron Patterson	2011-02-21	1	-5/+1
\|
*	Lock should be a unary node	Aaron Patterson	2011-02-21	1	-2/+2
\|
*	Allow database specific locking clauses to be used	Jesse Storimer	2011-01-20	1	-1/+5
\|
*	adding better tests surrounding limits in adapter visitors	Aaron Patterson	2011-01-03	1	-1/+1
\|
*	quoting limit nodes	Aaron Patterson	2010-12-07	1	-1/+1
\|
*	add locking support for postgres	Aaron Patterson	2010-10-13	1	-0/+4
\|
*	Make PostgreSQL play nice with its friends. (matches -> ILIKE instead of LIKE)	Ernie Miller	2010-09-29	1	-0/+8
\|
*	reordering order clauses :'(	Aaron Patterson	2010-09-23	1	-1/+9
\|
*	writing code that makes me sad	Aaron Patterson	2010-09-23	1	-1/+6
\|
*	adding a select statment visitor	Aaron Patterson	2010-09-23	1	-0/+27
\|
*	adding a postgres adapter	Aaron Patterson	2010-09-23	1	-0/+6