Michael A. Schoen wrote:
IOW, I'd rather that this patch NOT be applied -- in fact I think my
approach should be looked at with good humor, and then thrown away, in
favor of representing an executable sql statement as an array of
statement and bind values. With each connection adapter handling as
appropriate, interpolating in Ruby if necessary or using native bind
variables.
That approach will also mean changing how we generate UPDATE and INSERT
statements, since they are currently generated from scratch as literal
sql, and we'll want all the values to be bound.
So...all aboard? I'm game to attempt a real implementation, so long as
I've got core approval for a fairly substantial change to how sql's
passed around internally.
Also, could I get a 1-line code sample of how postgres bind variables
would be used?
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
