I'd like one (1) moon, and at least three to four stars, depending on
density and luminosity. Oh, and a bagel.
-Kyle
___
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core
Ticket #3692. Major bug with has_and_belongs_to_many relations.
Michael Koziarski wrote:
Hey guys,
We're now beginning to finalise rails 1.1, and we need to make sure
that we don't miss any heinous bugs. While we'll all be giving the
list a once over, we're only human and we're likely to mis
On 2/26/06, Michael Koziarski <[EMAIL PROTECTED]> wrote:
> We're now beginning to finalise rails 1.1, and we need to make sure
> that we don't miss any heinous bugs. While we'll all be giving the
> list a once over, we're only human and we're likely to miss things.
>
> So, if you have any tickets
So, if you have any tickets which you think need to be addressed,
please bring them up in this thread, or add a keyword of
needs_review. We're pretty keen on pushing out a 1.1 release pretty
soon, but we also want to get all the nasty bugs.
Today I started developing a new app from the trunk
Here's a few patches I'd like to see make it in:
http://dev.rubyonrails.org/ticket/3782 - Stop the MysqlAdapter crashing
when views are present (ignoring is better than crashing).
http://dev.rubyonrails.org/ticket/4108 - Alias the STI table to the name
of the association. Say Nationality uses
The patch has been applied to the trunk already.
--
Kent
On 3/8/06, Norman Timmler <[EMAIL PROTECTED]> wrote:
> Am Sonntag, den 26.02.2006, 16:16 -0500 schrieb Kent Sibilev:
> > Ruby 1.8.4 comes with soap4r 1.5.5. With this version of soap4r
> > actionwebservice is completely broken. Any soap rpc
Am Sonntag, den 26.02.2006, 16:16 -0500 schrieb Kent Sibilev:
> Ruby 1.8.4 comes with soap4r 1.5.5. With this version of soap4r
> actionwebservice is completely broken. Any soap rpc call which returns
> a value results with 'can't modify frozen object' exception.
>
> There is a ticket open for thi
How about http://dev.rubyonrails.org/ticket/3837 Add :dependent =>
:protect to has_many association (like ON DELETE RESTRICT).
It's really simple and I think it completes :dependent features to be
like the FOREIGN KEY Constraints of the DBMS. Patch is minor and
simple, and includes a test case.
I
On 3/6/06, Greg Lappen <[EMAIL PROTECTED]> wrote:
> I had the same thought after I requested this to be in Rails 1.1, but
> its not clear how plugins would work if we were using ActiveRecord
> outside of a Rails application.
You can create rails applications that don't use certain components
(such
I had the same thought after I requested this to be in Rails 1.1, but
its not clear how plugins would work if we were using ActiveRecord
outside of a Rails application. I guess this may not be an issue as
most folks are not using ActiveRecord outside of Rails, but until
there's a better OR
On 3/3/06, Greg Lappen <[EMAIL PROTECTED]> wrote:
> This may have gotten lost at the bottom of my email re: another topic
> so I'm repeating it again.
>
> How about that connection pooling adaptor for Rails 1.1?
>
> There is a patch attached to http://dev.rubyonrails.org/ticket/2162
> that's be
On Mar 4, 2006, at 3:58 PM, Keegan Quinn wrote:
On Wed, Mar 01, 2006 at 10:35:14PM -0600, John Sheets wrote:
I don't personally have the resources to set up an automated system
with access to a Sybase database, but I'll certainly keep up to date
with trunk and frequently run those unit tests ma
On Wed, Mar 01, 2006 at 10:35:14PM -0600, John Sheets wrote:
> I don't personally have the resources to set up an automated system
> with access to a Sybase database, but I'll certainly keep up to date
> with trunk and frequently run those unit tests manually. Perhaps
> there's a good Samari
This may have gotten lost at the bottom of my email re: another topic
so I'm repeating it again.
How about that connection pooling adaptor for Rails 1.1?
There is a patch attached to http://dev.rubyonrails.org/ticket/2162
that's been hanging out for a while, we'd love to see it make it i
On Mar 1, 2006, at 7:17 PM, David Heinemeier Hansson wrote:
If at all possible, please do
setup some form of automated testing for this adapter. Say a script
that checks out Active Record once a day/week, runs the tests, and
emails you if something is b0rked. That'd give us the confidence that
th
> Okay, finally got it cleaned up and working against recent trunk. The patch
Great work, John! It has been applied. If at all possible, please do
setup some form of automated testing for this adapter. Say a script
that checks out Active Record once a day/week, runs the tests, and
emails you if s
On Feb 26, 2006, at 2:08 PM, David Heinemeier Hansson wrote:How about the Sybase connection adapter? Any chance of getting thatinto 1.1? I can update the patch against the latest trunk andresubmit if that'll help. The patch only touches test code and addsa single new application source file, syb
> Supports use as either "oci" or "oracle".
Applied.
--
David Heinemeier Hansson
http://www.loudthinking.com -- Broadcasting Brain
http://www.basecamphq.com -- Online project management
http://www.backpackit.com -- Personal information manager
http://www.rubyonrails.com -- Web-application fra
David Heinemeier Hansson wrote:
It's always kind of bugged me that the Oracle adapter is named "oci",
seems odd relative to all the other adapters.
Would the core group be open to a patch that renamed this "oracle", w/
the required stubs to maintain backwards compatibility?
It's legacy from wh
~
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Bob Silva
> Sent: February 27, 2006 8:22 PM
> To: rails-core@lists.rubyonrails.org
> Subject: RE: [Rails-core] Rails
#x27;ll get it fixed up shortly.
>
>Bob Silva
>http://www.railtie.net/
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:rails-core-
>> [EMAIL PROTECTED] On Behalf Of Jeremy Kemper
>> Sent: Monday, February 27, 2006 6:32 PM
>> To: rails-cor
gt; From: [EMAIL PROTECTED] [mailto:rails-core-
> [EMAIL PROTECTED] On Behalf Of Nathaniel S. H. Brown
> Sent: Monday, February 27, 2006 8:12 PM
> To: rails-core@lists.rubyonrails.org
> Subject: RE: [Rails-core] Rails 1.1 is coming
>
> By date_helper you are referring to your time
http://nshb.net
~
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Bob Silva
> Sent: February 27, 2006 6:25 PM
> To: rails-core@lists.rubyonrails.org
> Subject: RE: [Rails-core] Rails 1.1 is coming
>
> Here's a few more trivia
32 PM
> To: rails-core@lists.rubyonrails.org
> Subject: Re: [Rails-core] Rails 1.1 is coming
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Feb 27, 2006, at 6:24 PM, Bob Silva wrote:
> > I'll also have the date_helper patch updated to trunk tonight. Not
> &
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 27, 2006, at 6:24 PM, Bob Silva wrote:
I'll also have the date_helper patch updated to trunk tonight. Not
sure
what's wrong with it yet but bitsweat asked for updated tests
against trunk
so...
Hey, it simply doesn't apply cleanly to trun
Here's a few more trivial patches that I run in a few apps without issues:
http://dev.rubyonrails.org/ticket/3952 - Adds additional contraints to
validates_numericality_of. Updated as per DHH's request to use long names
instead of abbreviations.
http://dev.rubyonrails.org/ticket/3506 - I just ad
ailto:[EMAIL PROTECTED] On Behalf Of Dr.Ernie
Prabhakar
Sent: Monday, February 27, 2006 9:43 AM
To: rails-core@lists.rubyonrails.org
Subject: Re: [Rails-core] Rails 1.1 is coming
Hi Benjamin,
On Feb 27, 2006, at 5:59 AM, Benjamin Curtis wrote:
> I'm probably one of two people using Rai
Hi Benjamin,
On Feb 27, 2006, at 5:59 AM, Benjamin Curtis wrote:
I'm probably one of two people using Rails who really cares about
the little annoyances that come with choosing to use primary key
field names of tablename_id. :) I don't know if it's 1.1 worthy,
but I would like some feedbac
I'm probably one of two people using Rails who really cares about the
little annoyances that come with choosing to use primary key field
names of tablename_id. :) I don't know if it's 1.1 worthy, but I
would like some feedback on http://dev.rubyonrails.org/ticket/3373 --
specifically, what
Please remember that almost everyone that uses Oracle knows exactly
what "oci" is. Also, "oci" isn't quite the best way of integrating
with Oracle anymore (although it does certainly work!), so I would
suggest having a stub named "oracle" and keeping the "oci" one as it
is until someone gets around
> It's always kind of bugged me that the Oracle adapter is named "oci",
> seems odd relative to all the other adapters.
>
> Would the core group be open to a patch that renamed this "oracle", w/
> the required stubs to maintain backwards compatibility?
>
> Or am I being too nit-picky?
It's legacy
So, if you have any tickets which you think need to be addressed,
please bring them up in this thread, or add a keyword of
needs_review. We're pretty keen on pushing out a 1.1 release pretty
soon, but we also want to get all the nasty bugs.
It's always kind of bugged me that the Oracle adapte
Ruby 1.8.4 comes with soap4r 1.5.5. With this version of soap4r
actionwebservice is completely broken. Any soap rpc call which returns
a value results with 'can't modify frozen object' exception.
There is a ticket open for this problem http://dev.rubyonrails.org/ticket/2553
There are several prop
I am voting for tickets #3811To be precise I am voting for fixing problem with :index in datetime select.In
http://dev.rubyonrails.org/ticket/3811 Bob made great job by consolidation all ticket related to date helper. I am using patch from this ticket on stage server and it works as expected (:in
> How about the Sybase connection adapter? Any chance of getting that
> into 1.1? I can update the patch against the latest trunk and
> resubmit if that'll help. The patch only touches test code and adds
> a single new application source file, sybase_adapter.rb.
>
>http://dev.rubyonrails.org
On Feb 26, 2006, at 1:13 PM, Michael Koziarski wrote:
Hey guys,
We're now beginning to finalise rails 1.1, and we need to make sure
that we don't miss any heinous bugs. While we'll all be giving the
list a once over, we're only human and we're likely to miss things.
So, if you have any tickets
Hey guys,
We're now beginning to finalise rails 1.1, and we need to make sure
that we don't miss any heinous bugs. While we'll all be giving the
list a once over, we're only human and we're likely to miss things.
So, if you have any tickets which you think need to be addressed,
please bring them
37 matches
Mail list logo
