This the same as
http://rails.lighthouseapp.com/projects/8994-ruby-on-rails/tickets/1692-setting-a-decimal-from-00-to-doesnt-constitute-a-change
which should be applied soon.
Fred
On 14 Jan 2009, at 03:52, stack wrote:
If you build a form to edit a model that has a decimal, you cannot
blank
I'm going to chime in mostly with what Chad said. I got interested
in the CI story for Rails itself a couple of weeks ago because I
simply could not get all the tests to pass on my own dev box, and
thought this was due to my own stupidity. It didn't take me long to
find out oh, the tests
On Wed, Jan 14, 2009 at 12:43, Mike Gunderloy larkw...@gmail.com wrote:
Integrity *may* be
able to replace cc.rb with superior awesomeness, but I'd like to see
someone set up a proof of concept with repro instructions. If anyone
goes down that path, I'll be happy to lend a hand by testing
I submitted a patch to lighthouse which caches columns (SHOW FIELDS)
for has_and_belongs_to_many associations. See the patch and ticket
at:
http://rails.lighthouseapp.com/projects/8994/tickets/1738-caching-columns-for-has_and_belongs_to_many
The patch is simple and unobtrusive, and resulted
We've been looking at switching to integrity as well. One of the major
benefits I see at the moment is that integrity would likely be more willing
to accept features.
On a separate note, I think it would be beneficial to have an easy, built in
way to run YOUR app against edge or latest of a given
2009/1/14 Mike Gaffney mr.ga...@gmail.com:
We've been looking at switching to integrity as well. One of the major
benefits I see at the moment is that integrity would likely be more willing
to accept features.
We are running the ci.rubyonrails.org off my ccrb GitHub branch, and
it's possible
Hi,
I stumbled upon an issue with migrations that's trivially fixable, and
has already been fixed in 2.2 (commit def594b92d1...) - But I'd love
to see it applied in a 2.1 (maybe 2.0?) point release. I am lost on
what to do to propose the fix, as it does not warrant IMHO opening a
lighthouse bug,
On Wed, Jan 14, 2009 at 3:59 PM, Gunnar Wolf gw...@gwolf.org wrote:
Hi,
I stumbled upon an issue with migrations that's trivially fixable, and
has already been fixed in 2.2 (commit def594b92d1...) - But I'd love
to see it applied in a 2.1 (maybe 2.0?) point release. I am lost on
what to do
