Ahoy!
Do you like patches? Well, it's your lucky day - 'cause there's one here!:
http://dev.rubyonrails.org/ticket/9913
The patch would allow aliasing tables so you could do something like this
(contrived example - the logic probably doesn't work quite right):
class Post < ActiveRecord::
Because the new simplified ActiveRecord::Base#inspect no longer
includes the memory offset, a series of ActiveRecord objects created
(without attributes) in quick succession will have the same inspect
value.
This makes #inspect insufficient for generating unique tokens. In
practice, this means cr
New patches have been added to the ticket. FYI
http://dev.rubyonrails.org/ticket/9899
On Oct 16, 10:42 pm, mikong <[EMAIL PROTECTED]> wrote:
> Exactly the kind of feedback I was hoping for. :)
>
> I'll apply most if not all of your comments. I'll have a closer look
> later after work, and expect
Thanks for quick reply.
--
Jacek
On Oct 17, 10:08 pm, "Jeremy Kemper" <[EMAIL PROTECTED]> wrote:
> On 10/17/07, Jacek Becela <[EMAIL PROTECTED]> wrote:
>
> > Below is a test case which shows strange fixtures behaviour (tested
> > against edge revision 7955). Is this behaviour correct or should
On 10/17/07, Jacek Becela <[EMAIL PROTECTED]> wrote:
> Below is a test case which shows strange fixtures behaviour (tested
> against edge revision 7955). Is this behaviour correct or should I
> fill a bug report?
This is expected behavior. Maybe this helps to understand:
topic = Topic.find(1)
Hello,
Below is a test case which shows strange fixtures behaviour (tested
against edge revision 7955). Is this behaviour correct or should I
fill a bug report?
class StrangeFixturesBehaviourTest < Test::Unit::TestCase
fixtures :topics
def test_disturbed_fixtures
topics(:first) # causes tr
>
> On 10/17/07, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> prompted by this, Ben Scofield proposed a similar patch:
> http://dev.rubyonrails.org/ticket/9542
> Which was rejected because it would violate roundtrips from classname
> to filename.
That makes total sense. Given that, I agree that mi
On 10/16/07, Scott Bronson <[EMAIL PROTECTED]> wrote:
>
> Right now, if you accidentally give a migration filename an upper-case
> character (say, 001-initialMigration.rb), you get a crash:
Was this file made from the migration generator or by hand? It seems like
we should fix this if it was som
Andrew White wrote:
> On 13 Sep 2007, at 23:53, Tim Lucas wrote:
>
>> Do you know which parts are currently broken, or don't work as
>> expected? AFAIK associations, STI and autoloading work just fine with
>> namespaced models.
>
> Associations do generally work but you have to be explicit about
On 10/17/07, Scott Bronson <[EMAIL PROTECTED]> wrote:
> Right now, if you accidentally give a migration filename an upper-case
> character (say, 001-initialMigration.rb), you get a crash:
>
>You have a nil object when you didn't expect it!
>You might have expected an instance of Array.
>
I am running rails 1.2.57919 on windows.
I access the internet via a http proxy; the env variable http_proxy is
set to http://user:[EMAIL PROTECTED]:port
gem works fine with these settings.
However 'script\plugin discover' fails:
C:/Install/ruby/lib/ruby/1.8/open-uri.rb:287:in `open_http': 407
11 matches
Mail list logo
