aboutsummaryrefslogtreecommitdiffstats
path: root/lib
Commit message (Collapse)AuthorAgeFilesLines
...
* Add database specific string concatenationKeenan Brock2016-01-055-1/+20
|
* Implement CASE Conditional ExpressionFelix Bünemann2016-01-055-1/+102
|
* Release 7.0.0Rafael Mendonça França2015-12-171-1/+1
|
* Inject the visitor rather than relying on other objects internalsSean Griffin2015-12-172-2/+7
| | | | | | This is ultimately messy no matter what, and increases the coupling to the database backend, but we can at least contain it somewhat into an object that's already coupled.
* Delegate to Connection Visitor in WhereSQL VisitorEdward Paget2015-12-171-1/+5
| | | | | | | | | | | | The WhereSQL visitor always uses the generic ToSQL visitor to create the where clause sql statement. This means that it'll miss database specific statements, such as 'ILIKE' in PostgreSQL. Since the `#where_sql` method is mainly used for ActiveRecord error reporting, this discrepancy could be confusing to users. This patch changes the WhereSQL visitor to use the its connection visitor to generate SQL for each statement in the SelectManager's wheres array. Then lets them be joined together with ' AND '.
* Merge pull request #369 from codeodor/patch-1Rafael França2015-12-171-1/+7
|\ | | | | Improve error message when passed unsupported type
| * Use a specific exception for unsupported visitsSammy Larbi2015-07-141-1/+7
| |
| * Improve error message when passed unsupported typeSammy Larbi2015-07-141-1/+1
| |
* | Merge pull request #381 from carsonreinke/function_orderRafael França2015-12-171-0/+1
|\ \ | | | | | | Add OrderPredications back into Nodes::Function
| * | Add OrderPredications back into Nodes::Function (removed with deprecation of ↵Carson Reinke2015-07-231-0/+1
| |/ | | | | | | Expression)
* | introduce predicate {does_not_}matches_regexp Keenan Brock2015-12-051-0/+8
| |
* | Add case sensitive regexpKeenan Brock2015-12-054-4/+19
| | | | | | | | | | | | | | Explicitly declare if this is case sensitive or not currently postgres assumes case insensitive regexp no other databases support regexps
* | Add case sensitive matchKeenan Brock2015-12-053-11/+15
|/ | | | | | | Explicitly declare if this is case sensitive or not most implementation assume case sensitive postgres assumes case insensitive
* Merge pull request #337 from yahonda/support_oracle12_top_n_2Aaron Patterson2015-07-143-2/+60
|\ | | | | Support Oracle 12c top-N query
| * Create Arel::Visitors::Oracle12 to provide better top-N queryYasuo Honda2015-06-192-0/+54
| | | | | | | | to support `FETCH FIRST n ROWS` and `OFFSET` for Oracle 12c database
| * Extract visit_Arel_Nodes_SelectOptionsYasuo Honda2015-06-191-2/+6
| |
* | Merge pull request #361 from evgenim/masterAaron Patterson2015-07-141-4/+10
|\ \ | | | | | | Fix visit_Arel_Nodes_FullOuterJoin/RightOuterJoin
| * | Fix visit_Arel_Nodes_FullOuterJoin and visit_Arel_Nodes_RightOuterJoin to ↵evgenim2015-03-161-4/+10
| | | | | | | | | | | | make them work with collectors.
* | | Follow up #370 for Oracle, to fix undefined method `expr' for 10:Fixnum bug.Eric Guo2015-07-141-1/+1
| | |
* | | No need to quote MySQL LIMITJean Boussier2015-07-101-1/+1
| |/ |/|
* | Dont need to quote limitArthur Neves2015-06-181-3/+3
| |
* | Move casted to its own fileVipul A M2015-05-312-40/+41
|/
* Special limited delete handling in MSSQLTamir Duberstein2015-02-232-2/+19
| | | | | Refernce: https://technet.microsoft.com/en-us/library/ms175486%28v=sql.105%29.aspx
* Delete should respect 'limit'Bradford Folkens2015-02-234-3/+11
| | | | | Conflicts: lib/arel/visitors/to_sql.rb
* Change the interface of `having` to match that of `where`Sean Griffin2015-01-276-16/+18
| | | | | | These two clauses have nearly identical semantics with regards to how they would be constructed as an AST. It doesn't make sense for their interfaces to be separate.
* Implement equality for `BindParam`Sean Griffin2015-01-251-0/+3
| | | | | It is impossible to test equality of things constructing trees with bind params otherwise.
* Change the version to 7.0.0.alphaSean Griffin2014-12-291-1/+1
|
* Allow a type caster to be given to the `Arel::Table` objectSean Griffin2014-12-295-16/+55
| | | | | | | | | This will allow most consuming code to avoid the deprecation introduced in 008445d6fd5f825d9b445ac75a7be67f0f7ab52c. The only code which will be affected is code that is building the `Arel::Table` object manually, rather than calling `arel_table` on an Active Record class. Hopefully this case will be rare enough that we don't need to introduce any additional APIs to work around it.
* Deprecate automatic type casting within ArelSean Griffin2014-12-261-0/+11
| | | | | | | | Rails now performs all casting eagerly, before passing the value into Arel. Once we remove this, the code on both sides will be simplified greatly. Ideally, we can provide the appropriate public APIs on the Rails side to ease this transition for library authors who depend on this behavior.
* Allow for handling quoted values in rangesSean Griffin2014-12-261-6/+14
| | | | | Since Active Record needs to eagerly cast values, we need to check for quoted infinity in our range handling
* {Matches,DoesNotMatch} support the ESCAPE clause with PostgreSQLKazuya NUMATA2014-12-251-2/+14
| | | | | to_SQL already has supported the ESCAPE clause in #318. PostgreSQL can use the ESCAPE clause too.
* 💣Sean Griffin2014-12-041-1/+1
| | | | `nil?` not `nil`
* Quoted nodes respond to `nil?` in the same way as `Casted` nodesSean Griffin2014-12-041-0/+1
|
* Quoted nodes respond to the same method as Casted nodesSean Griffin2014-12-041-0/+1
| | | | We need to be able to not care which we've gotten in ActiveRecord
* Don't re-quote nodes which are already quotedSean Griffin2014-12-021-1/+1
| | | | | | | | We're going to start working on removing type casting from arel. To avoid doing one gigantic commit which moves everything over to eager casting, we need a way to tell Arel that we've already cast it. The easiest path to that is to give it a quoted node, and then we remove this case once we're never returning a Casted node
* Remove `engine` from `TreeManager` and subclassesSean Griffin2014-11-298-26/+16
| | | | | | This constructor parameter was unused for everything except the convenience methods `to_sql` and `where_sql`. We can pass the engine into those methods directly.
* Remove engine from the constructor arguments `Arel::Table`Sean Griffin2014-11-291-40/+21
| | | | | | | | | | | | | | | It is never used outside of convenience methods which are only used in tests. In practice, it just made constructing tables more complicated on the rails side. This is the minimum possible change to remove the constructor argument, but continue to have the tests passing. I'm not sure if we have a reason to keep `project` and friends, and the solution might actually just be to remove the engine from `SelectManager` and friends. As such I've held off on deleting those methods. We need to figure out what to do with `Table#from`. It's old invocation, which read `table.from(table)` was certainly nonsensical.
* Remove deprecated method "Table#primary_key"Sean Griffin2014-11-262-17/+18
| | | | | | | The only place this method was still used is on the MSSQL visitor. The visitor has all of the objects required to inline this lookup there. Since the `primary_key` method on the connection adapter will perform a query when called, we can cache the result on the visitor.
* remove extra space before 'ORDER BY'Nihad Abbasov2014-11-261-1/+0
|
* Prepare for 6.0.0Rafael Mendonça França2014-11-251-1/+1
|
* Support Oracle bind parameter valueYasuo Honda2014-11-201-0/+4
|
* Use class objects rather than strings for the dispatch cacheSean Griffin2014-11-182-18/+10
| | | | | | | | The only reason we're using strings is to pre-populate the cache, but `Class#name` returns a new string instance on every call. This is a pretty major source of memory usage. We don't technically need to pre-populate the cache, and not doing so allows us to go back to using cache objects
* Add order to BindParams in the ToSql collectorSean Griffin2014-11-176-6/+21
| | | | | | | | | | | | This removes the need for us to do the re-ordering by walking the AST in ActiveRecord. We're using a block to communicate with the collector, since the collector needs to be the thing which knows about the index, while the visitor is the thing that needs to know the syntax. The BindParam needs to know about neither of these things, so it's been changed to stop being a subclass of SqlLiteral I could also see an alternative implementation using format strings if for some reason blocks cause a problem.
* cache the dispatch table on the depth first visitorAaron Patterson2014-11-102-6/+21
| | | | | We know the API for the depth first visitor in advance, so it's OK to calcuate this cache in advance
* oops! that should not have been checked inAaron Patterson2014-11-041-2/+1
|
* Look for `Enumerable` rather than `Array` in predicatesSean Griffin2014-11-021-2/+2
| | | | | It's not quite duck typed, but it will allow us to pass in our own objects with additional logic (like type casting).
* Revert "Revert "Merge pull request #300 from jpcody/master""Sean Griffin2014-10-311-4/+5
| | | | | | This reverts commit 9b92af7098b2728ced578ab9a7679176d20f120f. beta2 is out, and we've fixed the issue that this caused in Rails
* Bump to 6.0.0.beta2Godfrey Chan2014-10-301-1/+1
|
* Revert "Merge pull request #300 from jpcody/master"Sean Griffin2014-10-301-5/+4
| | | | | This reverts commit 36836fa5e7c084c0dce2818577e6fd0cf815f786, reversing changes made to 53bc8426648cc93695525e8f12102cd416b2d772.
* Dry up building quoted nodes in predicationSean Griffin2014-10-271-15/+23
| | | | | Given that we are going to remove casting from Arel in the near future, having a single place nodes in predications will help.
generated by cgit v1.2.3 (git 2.25.1) at 2024-10-11 08:39:09 +0000