No worries Ernie, just been one of those days.
I too, have been following Aaron's move on ARel for a long time too. I just
choose to learn C extensions in the past 6 weeks so I could provide a different
connection mode to the adapter that had strong encoding support, native ruby
bindings, etc.
Pragmatic advice Aaron, thanks!
- Ken
> Release a bugfix version that depends on AR ~> 3.0.0 and ARel ~> 1.0.0
> and you should be fine.
>
> --
> Aaron Pattersonhttp://tenderlovemaking.com/
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" gro
On Nov 15, 2010, at 7:07 PM, k...@metaskills.net wrote:
>
> Lastly (@Ernie), I do not think it's fair to say, just get your update
> out. Those who know me, know that I spent way to much of my free time
> writing open source code for the benefit of the rails eco-system,
> almost to a fault. This i
Pragmatic advice Aaron, thanks!
- Ken
> Release a bugfix version that depends on AR ~> 3.0.0 and ARel ~> 1.0.0
> and you should be fine.
>
> --
> Aaron Pattersonhttp://tenderlovemaking.com/
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" gro
On Mon, Nov 15, 2010 at 08:09:03PM -0500, Ken Collins wrote:
>
> Pragmatic advice Aaron. Thanks!
No problem. For some reason I have the "Priceline Negotiator" song in my
head now. ;-)
--
Aaron Patterson
http://tenderlovemaking.com/
pgpomRhGIyWz7.pgp
Description: PGP signature
Pragmatic advice Aaron. Thanks!
- Ken
> Release a bugfix version that depends on AR ~> 3.0.0 and ARel ~> 1.0.0
> and you should be fine.
> --
> Aaron Patterson
> http://tenderlovemaking.com/
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" g
On Mon, Nov 15, 2010 at 04:07:12PM -0800, k...@metaskills.net wrote:
>
> Koz,
>
> I can understand what your saying, especially from the internal
> interfaces of ActiveRecord to Arel and within the databases supported
> as part of rails core. But that should not be the only decision maker
> for a
Koz,
I can understand what your saying, especially from the internal
interfaces of ActiveRecord to Arel and within the databases supported
as part of rails core. But that should not be the only decision maker
for a gem versioning policy.
ActiveRecord/Arel are so tightly bound that a major versio
