On Nov 28, 2007 6:55 AM, James Adam <[EMAIL PROTECTED]> wrote:
> It's interesting, given that the reason it was decided to add all load
> paths before loading plugins was exactly to remove dependency
> problems! (see
> http://groups.google.com/group/rubyonrails-core/browse_frm/thread/7615e2ac0fa0
Hi,
Download free songs ..
Send songs to ur friends.
http://www.shakeelahmed.info/pakistanimusicmp3/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email
If I use :allow_blank => false I expect that no blanks are allowed,
however, they are allowed.
def test_validates_length_of_with_no_allow_blank
Topic.validates_length_of( :title, :maximum => 5, :allow_blank=>false )
assert !Topic.create("title" => "abcdefg").valid?
assert !Topic.
> My first choice would be to allow, even encourage, the group who does want
> to maintain and extend nested set functionality for Rails to add their
> improvements to the official rails nested set plugin. That would be the
> easiest way for anyone needing that sort of fundamental data
> structure
Andrew Kaspick wrote:
> :allow_blank is in 2.0 AFAIK, so that should do what you want
Ah. Yep. a search for allow_blank reveals
http://dev.rubyonrails.org/ticket/7383
Didn't catch that with my other searches.
--
Posted via http://www.ruby-forum.com/.
--~--~-~--~~~
:allow_blank is in 2.0 AFAIK, so that should do what you want
On 11/28/07, Greg Willits <[EMAIL PROTECTED]> wrote:
>
> So, here's a case something didn't work as expected, and I'm wondering
> if a feature tweak is worth considering.
>
> If I use :allow_nil => TRUE, validation rules still complain
So, here's a case something didn't work as expected, and I'm wondering
if a feature tweak is worth considering.
If I use :allow_nil => TRUE, validation rules still complain if a form
field is submitted empty (w/o using a presence_of rule).
So...
validates_format_of :first_name, :with => Is_h
On 11/13/07, Stephen Touset <[EMAIL PROTECTED]> wrote:
> 1 ) What, then, is the preferred mechanism for "seed" data in the
> database? Currently, many people use migrations to insert bootstrap
> data. If schema.rb will be used for tasks like db:reset, none of this
> data will be loaded.
I've writ
I typically don't use migrations for "seed" data; instead, I use
something like "rake db:bootstrap" or something like that.
Is there a reason you prefer migrations?
--Jeremy
On Nov 14, 2007 12:29 AM, Michael Koziarski <[EMAIL PROTECTED]> wrote:
>
> > 1 ) What, then, is the preferred mechanism f
WHO WE ARE
YouSendIt is the No. 1 digital file delivery company serving business and
individuals businesses who want a easy, secured, reliable and faster way to
SEND, RECEIVE and TRACK DIGITAL FILES.
YOUSENDIT SOLUTION
We replace the hassles of dealing with unreliable FTP servers, eliminate the
fr
Dear list,
Is it currently possible to use namespaces inside a resources block?
For example:
map.resources :projects do |projects|
projects.resources :tasks
projects.namespace :wiki do |wiki|
wiki.resources :pages
end
end
This should generate URLs as "project/:project_id/wiki/
pages/:pag
BTW, about the trailing slash, there is a inconsistency with the url_for
methods in Base and in UrlWriter (you can create urls with trailing slash
with one method but not with the other). This issue is addressed in a patch
here: http://dev.rubyonrails.org/ticket/9117
May someone take a look at it?
On 11/27/07, Chad Woolley <[EMAIL PROTECTED]> wrote:
> I think this is a fairly bad regression that will likely break a lot
> of plugins. We should consider fixing it before the 2.0 release. I
> can try to give a more detailed failure scenario if you want.
You're right about the load path being
Hi there,
I had a go at this, and managed to get it working. I'll probably
provide a plugin sometime in near future.
Stefan
On Nov 21, 5:24 pm, patrick aljord <[EMAIL PROTECTED]> wrote:
> On Nov 19, 1:02 pm, "Stefan Magnus Landrø" <[EMAIL PROTECTED]>
> wrote:
>
> > How would you expose this fun
On Nov 26, 2007 11:13 PM, Michael Koziarski <[EMAIL PROTECTED]> wrote:
> If there's an obvious successor to any of these plugins, we can update
> the README to tell people what they should be installing.
>
My first choice would be to allow, even encourage, the group who does want
to maintain and
15 matches
Mail list logo
