owed
>
> http://pastie.org/271354
>
> how do i extend ActiveRecord::Validations::ClassMethods, alternatively
> submit a patch?
Here are instructions for filing patches to the ticket tracker.
http://rails.lighthouseapp.com/projects/8994/sending-p
n AMo liked I probably said I would :)
Another thought I had was moving the association proxy and scoping
stuff from AR to AMo. See:
http://www.ideaforge.org/blog/?p=8#comment-67
--
Rick Olson
http://entp.com
http://lighthouseapp.com
--~--~-~--~~~---~--~~
You re
's existing app or
plugin. I'd suggest starting a git branch started and having folks
run it against their apps to see what breaks.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
Mime::Type
>
> Any comments?
According to the docs, you can skip request forgery protection by
skipping the before_filter:
skip_before_filter :verify_authenticity_token
Do you have any suggestions to make this easier for atompub implementors?
--
Rick Olson
http://lighthouseapp.com
h
might not be a bad idea though.
In a similar vein: last night at the Baltimore ruby group, John
Trupiano suggested some way of merging the yml files from the
geminstaller gem with Rails' gem configurations.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie
i_class_name is so that SomeMigration::User
writes "User" to the type field. AR::Base#compute_type shouldn't need
to create some custom name => class hash map or anything like that.
FWIW I've committed the original patch. See also:
http://rails.lighthouseapp.com/projects/899
up rake tasks
> that help simplify and solidify the patching process.
>
> Let me know what you think.
>
> Thanks,
> Scott
> >
>
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~
want to write. Then, you can just write
some ActiveBerkeley library using ActiveModel and mimicking
ActiveRecord's API where possible.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You rec
to implement some kind of voting, and allow it as a keyword
for searching:
"state:open tagged:patch votes:3+"
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message
l test case, we should be able to turn that into a regression
test before the patch can be re-accepted.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are
that supports the Rack interface. That's the approach taken with other
projects like Thin and Ebb: both of which look really cool.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You recei
ons. Please ask further
ones in the rubyonrails-talk forum. rubyonrails-core is for
discussion on future versions of Rails.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this mess
t; Comments anyone? Am I off-base or is this a bit ugly?
>
> cheers
> Perryn
The tests run at a lower level than the restful layer (which is really
just a set of routes mapping urls to controller actions).It
shouldn't require the default route though. I rarely non-
odel is parsed and sent as an UPDATE statement. This is not really
> desirable from a network or database standpoint.
Jeremy (bitsweat) has a plugin for tracking updates to ActiveRecord
attributes: http://code.bitsweat.net/svn/dirty/README It sounds like
this will be going into core. With that,
On Feb 2, 2008 12:19 PM, Rick Olson <[EMAIL PROTECTED]> wrote:
> Thanks for the input, everyone. I just committed it.
I also got another suggestion from Sven that the after_initialize hook
should run *after* the config initializers. That makes sense to me,
personally. So, please le
Thanks for the input, everyone. I just committed it.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on
On Feb 1, 2008 1:03 PM, Rob Sanheim <[EMAIL PROTECTED]> wrote:
>
> I think this would also fix this issue:
>
> http://robsanheim.com/2008/01/08/rails-observers-make-rake-dbmigrate-crash-from-version-0/
>
Well, let me know... that would be a plus.
--
Rick Olson
http://l
f any issues?
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group
h to not clone
> attributes in this case?
Being the genius I am, I couldn't find your ticket so I transcribed
your guerilla monkey patch to edge rails. I went to link up this very
topic in the ticket and finally saw that the patch number was in the
subject. Both patches seem to work fin
On Jan 23, 2008 7:41 PM, Lawrence Pit <[EMAIL PROTECTED]> wrote:
>
>
> > the portlet standard
>
> which standard? ;)
http://en.wikipedia.org/wiki/Portlet i suppose.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
ation with rails components
> and load any other already made component even if not done in Ruby.
Nope, sounds like plugin territory.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You rece
> One vote against, then. Anyone else?
A patch would be fine, it seems reasonable. Though, I don't really
see what it's hurting either.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---
se count?
count(:id, :conditions =>...) > 0
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core"
On Dec 19, 11:27 am, August Lilleaas <[EMAIL PROTECTED]> wrote:
> Please tell me if this has nothing to do on the rails core list. I
> have a feeling it does, though ; )
>
> I'm making an app that's using subdomains to authenticate. Hence, I
> set @request.host to something other than "test.host
On 12/17/07, Jay Levitt <[EMAIL PROTECTED]> wrote:
>
> On Thu, 13 Dec 2007 15:02:48 -0800, Rick Olson wrote:
>
> > We're talking about moving the Mephisto wiki (which is riddled with
> > spam) to a custom mephisto setup and appointing writers to maintain
> &g
On Dec 16, 7:41 am, giles bowkett <[EMAIL PROTECTED]> wrote:
> Requesting more info from the bug-reporter, I noticed this:
>
> > I just installed your utility belt on my laptop and it took
> > a while to realize that it was causing a very strange behavior on some of my
> > apps: The edit action
> Rick Olson wrote and ran precisely such a Q&A site over at railsweenie.com or
> some such and it was very active for a while but I guess eventually went
> dark. Maybe he'd be interested in passing the code off to you and dumping the
> existing data if he still has it a
Mephisto uses fixtures in a special db/bootstrap dir, and inserts them
with a db:bootstrap task. db:bootstrap includes schema:load and the
custom data. Though I agree that doing this in ruby would be
simpler...
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://m
s table_name # => 'bars'
end
end
class Foo < ActiveRecord::Base
class Bar < ActiveRecord::Base
puts table_name # => 'foo_bars'
end
end
I don't know if the generator should be updated, or maybe the docs
just need to be clarified a bit.
--
Rick Ols
e been a
> better choice myself, but oh well :)
Well then it would've loaded in front of 2.0.0, right? I think that's
why 1.99 was chosen.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~-
; => :monitorships, :name_prefix => nil
> end
> end
> projects.resources :posts, :name_prefix => 'all_', :collection =>
> { :search => :get }
> end
>
You set :name_prefix => nil for :topics.
> too far?
Seems to work for me. I tried exploiting it and all that too, but the
browser wasn't having any of that. Anyone else?
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You
> The last patch submitted against the ticket allows you to do this:
It just doesn't feel right to me to depend on your controller name for
this.
Let's try this as a plugin for now and give it a chance to live in the
wild. If this works out for folks writing JSON APIs, we can look at
including
for HTML so I'm not sure we have to
for JSON (and I think it's pretty rare that JSON is in HTML anyway).
Do you wanna whip up a patch with the right UTF codes?
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~-
On Oct 28, 12:43 pm, "Rick DeNatale" <[EMAIL PROTECTED]> wrote:
> Thanks to a great suggestion by Josh Susser. I've spent the past two
> days completely re-working the code I submitted in the eariler patch.
>
> The new patch;http://dev.rubyonrails.org/ticket/10012
> accomplishes the same result
> If we can be comfortable we're not introduce a security regression,
> then we can down to the talk about how we encode those values,
> whether it's sane to assume utf-8 encoded strings, and all that other
> good stuff :)
One thing to consider, too, is that this only affects JSON posted on a
web
On Oct 28, 5:01 am, Hongli Lai <[EMAIL PROTECTED]> wrote:
> On Oct 28, 11:02 am, "Michael Koziarski" <[EMAIL PROTECTED]>
> wrote:
>
> > As was mentioned by others, you should really be sending 201, so I'm
> > not even sure this is an issue that merits changing the documentation.
> > I realise
s ago, actually.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group,
EM version
(or not, if it's an edge-only plugin).
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core
to
override would be a cleaner implementation than passing a block too.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Grou
#x27;s a temporary condition put in place
until the transition is done, just keep it commented so it's obvious
what's going on. Smaller patches are easier to deal with.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~
it is a
larger job than it may initially look. Does someone want to give it a
shot?
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
path)
end
How about:
def prepend_view_path(path)
self.view_paths = superclass.view_paths.dup if @view_paths.nil?
view_paths.unshift(*path)
end
class ActionController::Base
self.view_paths = [default]
end
class FooController
prepend_view_path custom_foo_path
end
--
Rick Olson
http://light
ass
view_paths are the default, while the controller instances's
view_paths only affect that request:
def index
self.view_paths.unshift self.class.view_paths[params[:path].to_i]
end
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-
ed twofold. I also heard from the
> maintainer of Typo that he is planning on implementing Themer there.
I just saw that patch in trac last night. I think it looks
interesting, and I'll be taking a closer look at it later this week
when I get a chance...
--
Rick O
t;users"
>
> It might be more sensible to have a table_name of "security_users",
> though it irks me that it's the same result as the table_name for a
> SecurityUser class.
class Security < ActiveRecord::Base
class User < ActiveRecord::Base
end
end
Sec
On 9/9/07, Josh Peek <[EMAIL PROTECTED]> wrote:
>
> Just wondering how you are still using?
REST style controllers aren't a requirement in Rails. If REST becomes
mandatory, I can see where Verifications aren't necessary anymore
though.
--
Rick Olson
http://
> and if a patch to rework view_paths configuration in such way would
> be welcome.
I, for one, agree with your suggestions. I've committed the patch, it
looked good to me. Thanks.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-
t;
> What's recommended here?
The active resource unit tests use a mock request object for testing.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you
strategy
> was solid enough. I've used it enough times that I'm confident it
> works. I'll be releasing it for public consumption in the next
> couple of weeks.
Oh, I think coda hale had some similar plugin too. You guys should
totally team up!
--
Rick Olson
http://ligh
also have
a plugin that takes a slightly different route in caching frequently
accessed records in a single request.
http://activereload.net/2007/5/23/spend-less-time-in-the-database-and-more-time-outdoors
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-we
_controller.rb)
>
> I'm posting this to core because the routing behavior seems to be
> changing between 1.2.3, 1.2.3.update, and (soon) 1.2.4.
Nope, you can use named routes for your own conventions. Or better
yet, take the example of map.resources and write you
dex and show, but not the others; or I want
> to exclude destroy)
>
> Thank you.
>
> (I'm posting this to core since this only applies to later Rails versions)
ActionController::Resources does not provide a way to exclude routes
or use your own conventions. This isn&#x
Lame one-line fix until someone smarter than me comes up with one:
REXML::Document.class_eval { def doctype() nil end }
This hides any doctype so XmlSimple will ignore it. I think it's good
enough until this gets properly patched.
script/plugin install
http://svn.techno-weenie.net/projects/plu
On Aug 3, 10:55 am, "Daniel N" <[EMAIL PROTECTED]> wrote:
> On 8/4/07, DHH <[EMAIL PROTECTED]> wrote:
>
>
>
> > > I'm looking for a hot fix release, or a avoidance technique.
> > > (For example, How to disable the DTD for Rails XML Parser.)
>
> > Hi 3arrows,
>
> > Thanks for the report. I've imm
it's so some local variables are available in the init.rb
file: directory, lib_path, etc. Actually, they're now methods of the
Rails::Plugin class.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~
> Please open up a ticket with the failing test patch. I don't think
> modifying #write_attribute is the way to go though.
Er, nevermind: http://dev.rubyonrails.org/changeset/7238
Had a little Dr. House moment :)
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-ween
ame hash, which is why #reload doesn't change
anything.
Please open up a ticket with the failing test patch. I don't think
modifying #write_attribute is the way to go though.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-
veRecord::Base; end
=> nil
>> Customer::Tag.table_name
=> "customer_tags"
It's already working in edge, did you try it out? It's smart enough
to prefix the table name if the parent is an active record model, not
a regular module. Try this
. Otherwise it'd try to use html for everything. At any
rate, feel free to add some failing tests for the behavior you think
is correct, or come up with a patch to fix this.
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~--
e query cache unit
> tests run fine, and my app's running fine (i.e. tests are green). If
> anyone sees any issues with this please let me know. Hope everyone
> has a great weekend!
Cool, I'm sure other's still on 1.2.x will thank you.
--
Rick Olson
http://
complex queries. ez_where is pretty
cool, but I only use it in very rare instances. That's just my 2
cents I guess...
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this mes
, &block
end
end
class User < AR::Base
def accessible_property_find(*args)
Property.with_user(*args)
end
end
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message bec
separation in Rails and I'd hate to go back
> to spaghetti directory structure. I imagine that most of its users would
> feel the same, too.
Some of my larger plugins tend to look like that, though. It feels
wrong, I want to add directories to separate models and contr
ries << args
> execute_without_capture(*args)
> end
> alias_method_chain :execute, :capture
> end
>
> ActiveRecord::Base.connection.instance_variable_get("@queries")
I'm not sure, but I think that would leak memory like crazy :)
--
Rick Olson
http://lighthous
es :avatars
# /users/1/avatar, AvatarsController
map.resources :users do |user|
user.resource :avatar
end
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are su
gt; The other idea I liked was to create a method with the same name as the
> template and do a raise in it. I didn't test it, but that sounded like
> a good idea.
>
> Thanks for giving this some time.
What about #hide_action?
http://
> Any chance the 1.2-stable patch can be applied to that branch too?
> That's what we're aiming for.
There you go, Chris. Thanks for the patches :)
http://dev.rubyonrails.org/changeset/6651
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://
o not sure whether
> the patch works for floats and doubles as well.
>
> I'm not familiar (yet?) with the rails code or the C postgres/rails
> adaptor. Hypothetically speaking, if someone wanted to "fix" this,
> would they need to look at rails code, the post
have 1 anyway).
This should work:
http://dev.rubyonrails.org/changeset/6505
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
attribute that's either not allowed by
attr_accessible, or it's protected by attr_protected, so a mass
assignment won't work.
What about update_attribute name, value, true ?
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~---
e_base_path_for(file_name ||
> template), file_name || template, @assigns, template, e)
http://dev.rubyonrails.org/browser/trunk/actionpack/lib/action_view/base.rb?rev=6120#L514
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http:
ooking for any that match the beginning of
file_name. If none match, then just assume the first base_path (99%
of the time you'll only have 1 anyway).
Thanks for bringing this up!
--
Rick Olson
http://lighthouseapp.com
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~---
e
> would prefer. But, I'd love to have this fixed.
Well, the patch is outdated, but I have the tests merged. The
has_many patch was rejected so I still have to look at where that line
is being modified and add that to the edge version of the file.
--
Rick Olson
http://lig
because of the refactoring to
ActionController::Rescue :)
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" gro
eep
one eye on the changelogs (or subscribe to the various blogs reporting
on edge features, like http://ryandaigle.com/).
I fixed the app generator: http://dev.rubyonrails.org/changeset/6224
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~
/CHANGES, erubis 2.2
should work now. Is it only missing erb_variable or is there more
that needs to be done to rails?
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribe
ilfrog.com/
> Railfrog, the user-friendly, open-source web site deployment and
> content management system built with Rails; producing well structured
> and standards-compliant pages with Web 2.0 goodness.
Resource routes don't work with uncountable names. You need to hav
e no definite plans).
I was working with Ezra on erubis support when I committed that.
AFAIK, the erubis rails adapter still needs a few changes to allow it
to work with yield, and it should be ready as a drop-in replacement.
Er, I see Jeremy committed that. I think we were just working on
t;"admin/requests"}, diff: {:id=>/[^\/;.,?]+/}
>
> From this piece of code
> <% form_for(:request, :url => admin_destroy_requests_path, :html => {
> :method => :delete, :id => :adminDeleteForm, :name => :adminDeleteForm }) do
> |f| %>
>
> If
http://dev.rubyonrails.org/changeset/6120
committed. have fun (though, not with trac apparently).
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Cheers,
Martin
You need to sign up and log in to create tickets.
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" g
ts the ranges of the minutes that map to which
strings, rather than changing the tests to use to_f on the results of
1.year etc. If the latter approach is preferred, I'll whip up another
patch for it.
Applied. Thanks for staying on top of that.
--
Rick Olson
http://weblog.techno-ween
give you freedom to make modifications at your
leisure. A series of patches through pastie or trac does not make a
very good SCM substitute.
Believe me, I know :)
http://dev.rubyonrails.org/ticket/1758
Though sometimes it takes a bit to drill that notion into my head...
http://dev.rubyonrails.org/t
ran into that problem in Mephisto when you posted
the patch :)
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Core"
ick it up and determine if that were other http verbs that
should be used instead.
More work tomorrow, :)
I don't think that's necessary. UnknownAction should map to a 404
which should be sufficient I think.
--
Rick Olson
http://weblog.techn
ler.resource?" would be useful. Still need to investigate
if there is a nice way to grab the map routes from a controller.
I don't think that's necessary. It should just be a special exception
routing raises when a request doesn't match the correct request method
condition.
27;ve be working on a patch (http://pastie.caboo.se/31676) and it
seems to work fine. I just don't like the implementation of it. Seems
like it could be done much cleaner.
+1, it goes with the use of 406 Not Acceptable too.
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.
whichever way you like in
environment.rb. Plus, having it as a plugin now means folks can try
out the view_paths stuff without any commitment from core. If it's
really not a burden, maybe the rest of the plugin can be added to
core. Rails 2.0 is still a ways off.
--
Rick Olson
http://we
w
logic extracted into smaller methods such as
#lookup_template_base_path_for and #find_base_path_for. Is there any
way that we can just extract that and allow this view_paths plugin to
work without any hardcore jiggery-pokery?
--
Rick Olson
http://we
a little more clear than
opaque_name would work better though:
map.resources :quotes,
:controller => 'quote_requests',
:named_route => 'quote_requests'
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~
ests'
Or just call the controller QuotesController instead of
QuoteRequestsController. Is this really so bad? I'd think having the
shorter url and routes would be a plus.
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~-
Hey guys, I thought we were all ready for a new Rails 1.2 RC, but I
just realized I had cache_classes=true in one of my apps, and it
started bombing as soon as I changed it back. So here's the
changeset: http://dev.rubyonrails.org/changeset/5801
Nicholas' load_once_path changes were working, bu
"Foo.belongs_to([:bar])" blah blah
show_call_stack
show_call_stack 25 # shows more lines of the call stack
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are sub
found
http://www.codeplex.com/RORIIS/Release/ProjectReleases.aspx however.
It looks like it just packages FCGI and Rewrite ISAPI filters into a
nice installer.
Good luck :)
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You re
sts all ready to go.
> http://dev.rubyonrails.org/ticket/6808
shazam! http://dev.rubyonrails.org/changeset/5746
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed
migrate down, merge, migrate up, commit.
I agree, it does look complicated. I guess it depends on your
workflow though. Usually, I work solo or in a small team, so there
aren't a lot of branches. I haven't had any real issues with this as
> Sure. I'll get one done before the end of the weekend.
http://dev.rubyonrails.org/changeset/5476
AS tests all pass. All good? I'll merge this to stable if it is.
--
Rick Olson
http://weblog.techno-weenie.net
http://mep
I started
seeing the same memory increases and found it started after changeset
5223, the one that introduced ActiveSupport::Multibyte. Anyone else
seeing similar results?
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~~---~--~~
race, try overriding
ActiveWarehouse::Aggregate.autoloaded? so it returns false.
Also, please keep questions like this for the Rails list. This list
is for discussion on the core framework.
--
Rick Olson
http://weblog.techno-weenie.net
http://mephistoblog.com
--~--~-~--~~---
1 - 100 of 120 matches
Mail list logo
