lloeki/rebel
1
0
Fork 0
mirror of https://github.com/lloeki/rebel.git synced 2025-12-06 10:04:39 +01:00
Code Issues Projects Releases Packages Wiki Activity

Fix Arel name

Browse source
This commit is contained in:
Loic Nageleisen 2017-11-22 17:20:26 +01:00
parent 93592329de
commit a1084539af
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -7,7 +7,7 @@ You've been fighting yet another abstraction...
Aren't you fed up with object-relation magic? Aren't you fed up with object-relation magic?
But wait, here comes a humongous migration. But wait, here comes a humongous migration.
Is ActiveRecord making you sick? Is ActiveRecord making you sick?
To hell with that monstrous ARel expression! To hell with that monstrous Arel expression!
Tell the truth, you were just wishing Tell the truth, you were just wishing
That it was as simple as a here-string. That it was as simple as a here-string.
But could it keep some Ruby notation But could it keep some Ruby notation
@ -42,7 +42,7 @@ point of such a layer is entirely defeated. Concatenating and interpolating
only goes so far. only goes so far.
As ActiveRecord grows, a significant decision has been taken in the Rails team As ActiveRecord grows, a significant decision has been taken in the Rails team
to turn ARel into a library purely internal to ActiveRecord: the whole of it is to turn Arel into a library purely internal to ActiveRecord: the whole of it is
basically considered internal and private, and only ActiveRecord's public basically considered internal and private, and only ActiveRecord's public
interface should be used. Unfortunately, some highly dynamic, complex queries interface should be used. Unfortunately, some highly dynamic, complex queries
simply cannot be built using ActiveRecord, and concatenating strings to build simply cannot be built using ActiveRecord, and concatenating strings to build
@ -286,7 +286,7 @@ Yes. Just as you can write nonsensical SQL in SQL.
That's not a question. You're welcome to implement one that does though, and if That's not a question. You're welcome to implement one that does though, and if
it leverages the visitor pattern, allocates a trajillion objects along the way it leverages the visitor pattern, allocates a trajillion objects along the way
and manages to produce invalid SQL in some corner cases, well congratulations and manages to produce invalid SQL in some corner cases, well congratulations
for reimplementing ARel. for reimplementing Arel.
## License ## License