All,
There's a bit of behavior I'd like to tweak around the
find_or_create_by methods to help make it more obvious when a
developer (especially newbies) screws up by forgetting to initialize
required fields. Let's say you have some code like this:
car = dealership.cars.find_or_create_by_model("
On Sat, Apr 4, 2009 at 6:25 AM, Michael Schuerig wrote:
>
>
> Raising ActiveRecord::StatementInvalid as the single exception for
> anything that might go wrong is rather unspecific. There are
> differences between exceptions, some signify plain programming errors,
> others are caused by potential
Man, I'd *love* that. Specially considering the possible race
conditions of validates_uniqueness_of.
On Fri, Apr 3, 2009 at 1:25 PM, Michael Schuerig wrote:
>
>
> Raising ActiveRecord::StatementInvalid as the single exception for
> anything that might go wrong is rather unspecific. There are
> d
Hi Allen,
I read your proposal and it looks interesting. Rails scaling was a
very hot topic in the community around last year I think. Apparently
twitter was having problems scaling with a single database, but a
quick solution was found (I think that it was a 75 lines of code
plugin). I don't know
Raising ActiveRecord::StatementInvalid as the single exception for
anything that might go wrong is rather unspecific. There are
differences between exceptions, some signify plain programming errors,
others are caused by potentially recoverable faults. Specifically among
the later are violatio
Thanks for the suggestion Allen. Considering the scalability of this
solution, I'm thinking on use starling to handle the asynchronous
calls. Starling by itself is a perfectly scalable solution that allows
you to add separated servers to handle asynchronous messages. My
plugin should provide an ea
I can't replicate this here - I created a dummy class in a plugin,
with a method that raised an exception, then called that method in a
controller method from the app. I see the stack track in the response.
On Apr 3, 9:01 am, Peter Marklund wrote:
> Hi!
> Has anyone experienced that stack traces
Sorry for the late response. I posted one earlier, but it looks like
it got moderated and I'm not sure why. Anyways, thanks for the
suggestions. It is a big concern for me that I put this into the right
place in the rails framework, whether it be directly integrated or
handled as an attachment. I
XRDS is in the process of being obsoleted, to be replaced with XRD.
Although the spec is not complete, new applications would be well
served by moving to XRD. It's been blogged extensively here:
http://www.hueniverse.com/hueniverse/xrd/
Gregg
--~--~-~--~~~---~--~~
One thing I'd like to suggest is that, at least for me, it would be
useful if this kind of work could be passed off to another machine to
handle. I know this request drastically increases the work load, but I
think it would be beneficial to have a setup where one box handles
server-to-client and a
Hey Carlos,
I'm currently doing a school project where we are creating two rails
applications that are going to talk to each other. When I was
researching some stuff I found some basic auth stuff that was build
into rails. I think this is a very viable way to handle authentication
when requesting
Hi!
Has anyone experienced that stack traces are missing when exceptions
are raised in plugin code? We started having this issue when upgrading
from Rails 2.1 to Rails 2.3.2. If I move the code into the application
I get the stack trace back. Any ideas what could be causing this? How
is Rails inte
12 matches
Mail list logo
