All this stuff with ports, multiple definition of hosts etc. make me crazy.
Completely agree with you, it should be somehow more integrated with
default config and follow CoC.
вторник, 22 января 2013 г., 0:10:02 UTC+4 пользователь ChuckE написал:
Concerning
This is something which is not exactly a Rails issue, just something Rails
(as well as most of the other frameworks including jQuery library)
contribute to.
Let's consider I have a form which creates a resource on my web-client. It
posts the form on submission to a create endpoint on a certain
+1. The same update statement would work for MySQL as well.
Just a small thing: don't forget to take the updated_at timestamp into
account in your patch. Just mentioning in case.
Segunda-feira, 21 de Janeiro de 2013 0:56:37 UTC+1, ajsharp escreveu:
The method is here:
I may be wrong but that's my understanding: #increment happens at instance
level, so it takes into account the current value at that particular
instance, whereas .update_counters is just a straight sql query, so it can
operate using column + value directly. If you want to allow the database to
I understand what you mena. However, how would one handle such an increment
on concurrent threads/processes? You do have to handle the ambiguity
somehow. Delegate the responsibility to the DB sounds reasonable, but some
more inputs would be nice.
Segunda-feira, 21 de Janeiro de 2013 0:56:37
It sounds like an interesting idea but I have some concerns. How about
value stored in AR instance? You wouldn't know what value was saved to
database unless you reload the record.
Pranas
On Tuesday, January 22, 2013 8:15:16 AM UTC-8, ChuckE wrote:
I understand what you mena. However, how
But increment is inherently subject to concurrency issues, and the only way to
safely avoid them is to use a row level lock when incrementing the value, which
presents a whole host of complications of its own.
Cheers,
Alex Sharp
On Jan 22, 2013, at 7:00 AM, Carlos Antonio da Silva
On Tue, Jan 22, 2013 at 10:39 AM, Pranas pranas.kizi...@gmail.com wrote:
It sounds like an interesting idea but I have some concerns. How about
value stored in AR instance? You wouldn't know what value was saved to
database unless you reload the record.
Yea, good point, the DB does not
On second thought, ignore most of what I've said about the updated_at
timestamp. The current method *does* update it (which is your point I
glossed over), so that would need to be carried forward. I still find the
general behavior of things skipping that timestamp a little headscratching,
On Tuesday, January 22, 2013 1:05:50 PM UTC-8, ajsharp wrote:
By bust the cache, do you just mean update the counter?
I was referring to updating the updated_at timestamp, as the default
ActiveRecord #cache_key integrates that column if available to help ease
your cache expiration. In this
I've installed bootstrap-sass, and added an @import line in my css. Rails
won't find or serve up the bootstrap files. One error msg on the Mozilla
console says:
The stylesheet http://localhost:3000/assets/bootstrap was not loaded
because its MIME type, application/javascript, is not
Please direct questions about Rails to Rails Talk:
https://groups.google.com/forum/?fromgroups#!forum/rubyonrails-talk (i see you
already have) or to StackOverflow. This list is for the programmers who work on
the framework itself.
--
Richard Schneeman
http://heroku.com
@schneems
Hi Per,
This is a question better suited for the rubyonrails-talk mailing list. This
list is reserved for discussions about the core of Rails, whereas
rubyonrails-talk is for application support QA.
Thank you!
On 23/01/2013, at 16:07, xscr...@gmail.com wrote:
I've installed
13 matches
Mail list logo
