Here is the file
http://jibwa.com/samples/dangerous_nested_attributes.rb
here is the article
http://jibwa.com/code-and-documentation-for-programmers/rails-nested-attributes-custom-modific.html
On Apr 5, 6:10 pm, Josh wrote:
> I can agree that its dangerous to destroy attributes in this means,
>
I decided to write up a bit more of a description:
http://www.somethingunimportant.com/2009/04/06/rails-bug-found-while-streaming-output-in-actioncontroller-tests/
On Apr 5, 1:19 pm, Andrew Bloom wrote:
> I'm just trying to get people aware of my new patch. It's a very
> simple update to TestPro
Ticket #390 just got resolved and committed, which implements more
complete table name quoting than I had:
https://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/390-postgres-adapter-quotes-table-name-breaks-when-non-default-schema-is-used
However, that patch still doesn't quote tab
On Apr 5, 5:17 pm, Isak Hansen wrote:
> You're not quoting the schema name?
Correct. Apparently the schema name should not be included in the
quotes. Here's an example (PostgreSQL 8.2.11):
test=# create schema schema_test create table "CamelCase" (id integer
primary key);
NOTICE: CREATE TABLE
I can agree that its dangerous to destroy attributes in this means,
but for my case there is no other way, and each record is only
modified by one person at a time anyways. I realized my code above for
a workaround was wrong and without the ability to know what
association ids were updated its eas
On Sun, Apr 5, 2009 at 1:40 AM, Scott Woods wrote:
>
> We have a legacy database that has been migrated to PostgreSQL and
> includes camel-case table names. When running migrations, the schema
> dumper throws an error when it encounters these tables. I believe I've
> created and tested the proper
I'm just trying to get people aware of my new patch. It's a very
simple update to TestProcess that allows testing of streaming output.
Before my patch TestProcess tries to build an HTML::Document with the
Proc instead of the captured output of the Proc. I've put this
together against tags/2.3.2.1,
>> Nice work on the accepts nested attributes for, I've been waiting for
>> this for a while and haven't had the time to write it.
>>
>> I am curious to know about the feature for deleting attributes. For a
>> lot of reasons, I prefer to just not send back the items I want
>> deleted. Do you think
It would also cause problems if you have a multi-user environment. User 1
downloads the form, User 2 completes an edit form that adds a new
association to the collection, User 1 posts their form without having record
of the newly created record from User 2 --> User 1 accidentally deletes User
2's
On Wed, Apr 1, 2009 at 7:02 AM, Joseph Palermo wrote:
>
> I've got a route:
> map.find_stuff "/find_stuff/:near", :controller =>
> "find_stuff", :action => "show"
>
> Where the :near portion is user specified, so when users enter a place
> with a period, the route doesn't match correctly. So I c
On Sun, Apr 5, 2009 at 4:27 PM, Josh wrote:
>
> Nice work on the accepts nested attributes for, I've been waiting for
> this for a while and haven't had the time to write it.
>
> I am curious to know about the feature for deleting attributes. For a
> lot of reasons, I prefer to just not send back
11 matches
Mail list logo
