On Sep 30, 3:15 pm, Tarmo Tänav <[EMAIL PROTECTED]> wrote:
> On E, 2007-10-01 at 10:02 +1300, Michael Koziarski wrote:
>
> > Hi there,
>
> > Inserting empty records has been handled, in a different way, in edge
> > rails, this will work in 2.0.
>
> Actually it hasn't been fixed, there was an attempt
> with:http://dev.rubyonrails.org/ticket/9253
> But it ran into a problem with databases that needed primary key
> prefetch and the ticket is currently waiting for some ideas on
> how to approach the issue.
>
> I think I could get the patch to work by just keeping the PK prefetch
> and going with the insert_record(table_name, attributes) but I'm not
> even sure anymore if that would be a good approach.
>
> Perhaps the easiest fix would be to just let the adapters implement
> insert_blank_statement() (so they could each provide their way of inserting
> a blank row) and generate the SQL in AR::Base.create() in case there
> are no columns to insert.
>
> Any ideas?
>
> --
> Tarmo Tänav <[EMAIL PROTECTED]>
Dear Tarmo,
I am new to the list; but I am starting to wonder how many core
rails developers are using Postgres versus other databases? What is
the status of support/quality of the various database drivers compared
to MySQL, which seems to be the dominant server?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---
