Not sure if it'll help you or not (especially since there isn't an
ActiveRecord driver yet) but my new Mysql2 gem forces the use of UTF-8
for connections to MySQL as well as strings in 1.9 -
http://github.com/brianmario/mysql2
I'll be working on and releasing an ActiveRecord d
Forgot to mention I'd also like to try and find a creative way to not
have to forcefully require the JSON gem (activesupport/lib/
active_support/json/encoding.rb:13) even if the coder never intends on
using it.
-Brian
On Jan 20, 9:34 am, brianmario wrote:
> I'd also like to wrap
nabling it as a backend) is up to
date as of rails 2.3.5 and from what I can tell in the code in Rails 3
it may be compatible with it as well. http://github.com/brianmario/yajl-rails.
The link to the yajl-ruby ticket is:
https://rails.lighthouseapp.com/projects/8994/tickets/2666-yajl-ruby-as-a-json-
I've updated the LH ticket with another patch - finishing off the
changes to actually parse from the IO (instead of converting to a
string first) for the rexml, libxml and nokogiri backends.
Should this be in another ticket?
-Brian
On May 17, 9:54 am, brianmario wrote:
> Thanks for co
If I'm remembering correctly, you should be able to override this in
your localization yaml files for your project.
The keys of interest for what you're wanting to do are here:
http://github.com/rails/rails/blob/6d4a4fa04c20cee51c4e374045cc75e2ec16/actionpack/lib/action_view/locale/en.yml
All
May 16, 8:34 pm, brianmario wrote:
> Done:https://rails.lighthouseapp.com/projects/8994/tickets/2659-paramspars...
>
> Let me know if you need anything else.
>
> -Brian
>
> On May 16, 7:22 pm, Joshua Peek wrote:
>
>
>
> > Yeah, create a LH patch and assign it
May 16, 2009 at 6:01 PM, brianmario wrote:
>
> > Ok I forked and patched the ParamsParser to just pass request.body to
> > the parsers. I did it for JSON, XML and YAML (using YAML.load_stream
> > instead of just load).
> > I also patched the XmlMini and JSON decoders for
c/mocha but
no idea using Test::Unit.
Here's the commit:
http://github.com/brianmario/rails/commit/c63703489eb1f3f4dd96885e1e223126e5208638
Feedback?
Also, should I make a lighthouse ticket for this?
-Brian
On May 16, 9:44 am, Mislav Marohnić wrote:
> On Sat, May 16, 2009 at 09:54,
Exactly.
What's the next step here?
I can fork Rails and work on a patch, though I'm unsure how many/which
tests will need to be refactored.
On May 15, 10:40 pm, Michael Koziarski wrote:
> > I guess the real patch would allow "ActiveSupport::JSON.decode" to
> > accept an IO object as well. Then
ct the request params in your
> middleware and Rails will be fooled into using that instead.
>
>
>
>
>
> On Fri, May 15, 2009 at 1:31 PM, brianmario wrote:
>
> > Hey everyone,
> > I was wondering what the possability was of changing these lines:
>
> > body
Hey everyone,
I was wondering what the possability was of changing these lines:
body = request.raw_post
Hash.from_xml(body)
or
data = ActiveSupport::JSON.decode(body)
to instead be handed the env['rack.input'] IO itself?
Being as though both calls (from_xml and decode) are handled by rails
else
11 matches
Mail list logo
