These are just small things, but I noticed that the radio_button
really sucks when using with a fields_for or form_for block. First,
it ignores the :index option passed into the parent fields_for when
generating its ID! Second, you cannot use f.label to target it. I
fixed both of these:
http:/
On 17 Feb 2009, at 07:03, ritu wrote:
>
> Hi All,
>
> I was finding issues with mongrel. As I know, It handles/processes one
> request at a time. I searched it on net and found that its not mongrel
> which handles single request at a time. Its rails which handles one
> request at a time whereas
Hi All,
I was finding issues with mongrel. As I know, It handles/processes one
request at a time. I searched it on net and found that its not mongrel
which handles single request at a time. Its rails which handles one
request at a time whereas mongrel can handle multiple request. But
nothing was
You mean like the 'id' column?
On Feb 15, 9:42 pm, Will Bryant wrote:
> non-constant default values is a thing that not many people use with
> an ORM layer, and does not fit well into the ORM lifecycle; for
> example, it is expected that when you initialize a new record, the
> attributes on that
