`1.week.days` is what you're looking for. I don't think an alias would be
necessarily bad, though. It's similarly done elsewhere.
On Thu, Mar 5, 2020 at 5:58 PM Jason York wrote:
> Hi! Would it be valuable to add some convenience methods to Duration to
> convert the value to years, months, days?
Would this alias Array#excluding? I think the Array#except is natural and I’ve
found myself asking why it’s not aliased already many times but I’m not the one
to ask. 🙂
Sent from my iPhone
> On Feb 25, 2020, at 10:21 PM, Alex Golubenko
> wrote:
>
>
> Hi guys!
>
> Time to time I meet quest
Hi Thushara,
Just to double-check: Is your database indexed correctly? Have you tried
plugging in something like lol_dba gem to spot missing indexes?
Sent from my iPhone
> On Feb 25, 2020, at 10:21 PM, Thushara Wijeratna wrote:
>
>
> Hi All,
>
> I have a Rails app (rails version 5.2.4.1 /
7abb-1b91-4eea-978e-5a483c2e30a7%40googlegroups.com
> <https://groups.google.com/d/msgid/rubyonrails-core/a6c37abb-1b91-4eea-978e-5a483c2e30a7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
Hello from Minneapolis Josh Brody (952) 239-7408 www
<http://
Thanks Dmitry, your store_model gem looks particularly well done. I'll give
it a try!
On Wednesday, October 2, 2019 at 12:31:04 AM UTC-5, Dmitry Tsepelev wrote:
>
> Hi Josh!
>
> There is a number of gems that can do this (or similar) thing for you:
>
> - https://gi
ing I should look into or are there
technical/philosophical reasons why this would not work? Thanks in advance.
- Josh Marchello
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from this group and stop receiving
ee a
PR or issue. It's something I'd be interested in at contributing to, if
only for the selfish reason of reducing my own burden.
--
Josh
--
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To unsubscribe from thi
I am working with a collection of objects that have a growing number of
states. Each state requires a different layout/html wrapper. To reduce the
need for conditional statements within the partial or template, I thought
it might be nice if the layout option could be set dynamically using a proc
My understanding is that Rails was moving away from CoffeeScript and
towards modern JavaScript. This seems like it would be a welcome addition.
On Tuesday, July 10, 2018 at 8:28:18 PM UTC-4, Ryan Castner wrote:
>
> Hello all,
>
> I made a post on the issue tracker (
> https://github.com/rails/rai
I have a form with a select_tag and options_from_collection_for_select that
I can't seem to get to pass. The parent object, Campaign, saves but does
not associate with the child-object Uploadzip.
Campaign has_one Uploadzip Uploadzip belongs_to Campaign
There's also the campaign_id foreign_key
Hi,
I was just wondering if there would be any reason I shouldn't do this, like
problems with tags or something. Currently we're taking Cookies and
CookieStore and inserting them before Logger in the stack, which feels just
a tad more dangeresque than moving the logger to the bottom of the stac
ingful message names. The
problem with passing around procs is that you can't tell anything about
them - they are just procs, and calling them looks like like calling any
other proc. A simple duck-type for secret tokens will give you more
flexibility and make it easier for others to understand a
I dislike this. I'd rather see something along the lines of `present?` that
can be tacked on anywhere. Maybe something like this:
company = current_user.company.present!
--
Josh Susser
http://blog.hasmanythrough.com
On Tue, Sep 24, 2013 at 2:58 PM, Roman wrote:
> Hi,
> just st
You are looking at one particular case where the IdentityMap[1] pattern
would be a solution. There are plenty of other cases, including reciprocal
associations (which is currently partly addressed by the :inverse_of option
on association). There was a Ruby Summer of Code project for doing an
Identi
lymorphism in one query, one way is to use
has_many :through with an STI associated model.
--
Josh Susser
On Saturday, September 8, 2012 at 4:30 AM, ChuckE wrote:
> Hi,
> I'm currently having the situation where I have to implement a polymorphic
> has_and_belongs_to_many by i
d Ruby idiom for the inverse of `if object.nil?` is `if object`.
Yes, there is an edge case when object == false, but other than that it works
great and should be how you write your code. There is no need for another
method that just makes code wordier and harder to read.
--josh
> среда, 15
abstraction, and is
especially helpful for polymorphic associations. If the new ARel-based query
API enables this to be done without changing a bunch of other things, I'm all
for it.
--
Josh Susser
On Tuesday, August 7, 2012 at 8:23 AM, Peter Brown wrote:
> Hi,
>
> Guillermo asked m
Hiya,
So, what was the impetus behind having ParamsParser create Date and
DateTime objects out of application/json requests? The project I'm on
expects parameters to be received as standard types (bools, numbers,
strings, arrays, and hashes). Rails shouldn't try to convert objects that
are e
@Olek,
I think they should; just like most other aspects of Rails, I think the
developer should be able to choose what to include. An added benefit of
extracting this into a separate gem is that it'll likely encourage more
active development on Rails fixtures themselves because it won't be coup
setup.
It might make sense to extract the fixture stuff into a gem so it can be more
loosely coupled, but I'd expect resistance to removing the feature entirely.
--
Josh Susser
http://blog.hasmanythrough.com
On Thursday, July 5, 2012 at 11:48 AM, Olek Janiszewski wrote:
> Hi guys,
&
On Friday, April 13, 2012 at 1:34 PM, Rodrigo Rosenfeld Rosas wrote:
> Em 13-04-2012 17:30, Josh Susser escreveu:
> > The best way to set up a staging server is for it to be configured as
> > close to production as possible, so I always run my staging server
> > us
does story
acceptance. But I don't expect that to become standard in Rails. I think
development, testing, and production are really the only ubiquitous
environments I've seen, and are exactly the right set for Rails to include as
standard.
--
Josh Susser
http://blog.hasmanythrough.
ngs that are embedded in a web page and get downloaded by the
browser. This includes images (JPGs, PNGs), javascript files, CSS files, flash
movies, mp3s, etc. Since locales are used only by the server and not downloaded
by the browser, they are server configuration, not assets.
--
Josh
t how they want to
manage that.
--
Josh Susser
http://blog.hasmanythrough.com (http://blog.hasmanythrough.com/)
On Thursday, November 17, 2011 at 10:25 AM, Aaron Patterson wrote:
> We need to do something about our changelogs. First I will explain the
> problem, then I will propo
Interesting idea. I'd suggest making sure that the exception classes are
subclasses of ActiveRecord::RecordInvalid, so that rescue clauses can either
care about the specific validation or not.
--
Josh Susser
http://blog.hasmanythrough.com
On Mon, Aug 22, 2011 at 7:10 AM, André Silva
sk him but forget to when I get the chance.
--
Josh Susser
http://blog.hasmanythrough.com
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" group.
To post to this group, send email to rubyonrails-c...@googlegroups.com.
To unsubscribe
re were enough demand that
might make it into Rails itself, but I don't see the need for that yet.
--
Josh Susser
http://blog.hasmanythrough.com
--
You received this message because you are subscribed to the Google Groups "Ruby on
Rails: Core" group.
To post to this group,
ine without undoing the
other migrations. Madness!
There's also the improbable but pathological case where a migration in
an engine has the same version number or class name as one in the main
app or another engine. Now that I've said that I realize that
migrations in engi
y done, but it's not
dependent on them.
I'm starting to work on some patches for these changes, but I thought
it might be worth throwing it out there for a reaction before getting
too deeply into it.
--
Josh Susser
http://blog.hasmanythrough.com
--
You received this message
I read the Rails 3 Beta call email and I wanted to try to raise this ticket
again to maybe get it a bit more visibility before the beta comes out.
Anyone feel like commenting on this patch? I've found it helpful, anyway!
On Tue, Jan 5, 2010 at 2:38 PM, Josh Symonds wrote:
> Th
nts, like you said. In making the
patch I figured the amount of people who would be helped by the performance
improvements probably outweighs the number of people who have associations
named "except." But hey, I could be wrong.
Josh
On Tue, Jan 5, 2010 at 2:30 PM, Jeremy Evans wrote:
> On
I made a patch to allow eager loading to exclude specified columns on the
eagerly-loaded models. If you have a model that you want to load for a
specific reason -- like, say, you have lots of users, and you want to grab
all their posts but exclude the posts' bodies -- you can now specify that by
go
this is
just to make Ruby act more like Perl where empty strings are false-ish
values. I'm sure there are other use cases for #presence, but empty
strings that come from form submissions seem like at least 90% of the
issue.
--josh
On Dec 28, 2009, at 7:07 AM, Rick DeNatale wrote:
&g
rails bug tracker (https://rails.lighthouseapp.com/projects/
8994-ruby-on-rails/tickets/3603). This is my first patch I have
submitted to rails so I would really appreciate any comments and
feedback.
Thanks,
Josh
--
You received this message because you are subscribed to the Google Groups "
y in TestNestedAttributes and
TestAutosaveAssociation, so I don't think it's widely used.
Thoughts?
Thanks,
Josh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" grou
Forget []. I do need to know if #attributes is available on an
ActiveModel instance.
On Sep 1, 9:26 am, Josh wrote:
> Is the AMo lint test up to date?
>
> I'm writing a new-feature patch and I need #attributes and [] (that
> is, my_object["foo_attribute"] to be defin
On Sep 1, 9:26 am, Josh wrote:
> Is the AMo lint test up to date?
>
> I'm writing a new-feature patch and I need #attributes and [] (that
> is, my_object["foo_attribute"] to be defined, but I don't see them in
> the lint test. Seems like the lint test is r
Is the AMo lint test up to date?
I'm writing a new-feature patch and I need #attributes and [] (that
is, my_object["foo_attribute"] to be defined, but I don't see them in
the lint test. Seems like the lint test is rather short, is that all
it takes to be an AMo instance?
Thanx!
--~--~-
line of code in the scaffolding bears a
maintenance cost, and it seems better to keep it easy to upgrade than
make it feature-complete for end-users.
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~---~--~~
You received this message because you are
ready-exists
Thanks!
Josh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this group, send email to rubyonrails-core@googlegroups.com
To unsubscribe from this group
world, etc. Maybe a lot of developers don't want to
think about users and permissions, but for security standards and
awareness I think that this should be at least mentioned in the
configuration especially on a shared hosting account, world
writable, scary!
-Josh
On Jun 9, 7:47 pm, Jo
I am running rails on mongrel with RHEL5 and I have a curious issue
with the file permissions set when I upload a file and store it to my
uploads storage folder. I have the uploads storate folder set to
drwx-- owned by my user who is running mongrel. When the files get
written they come out -r
. Also, Nathan Sobo's Unison is a very interesting take on
integrating a relational algebra into AR associations (which I think
he started as an offshoot of ARel).
--
Josh Susser
http://blog.hasmanythrough.com
Golden Gate Ruby Conf :: April 17-18 :: http://gogaruco.com
--~--~-~--~~---
gt; although the names/ids are still verbose there's no way around it
>
> 2) the whole blank association thing isn't quite obvious. i have
> ":reject_if => {|h| h.values.all?{|v| v.blank?}}" of course, but this
> pattern of hanging blank objects off the parent in
params/xml block representing every control, some
with ids and _deleted, others just blank. Sending back blank data for
all 300+++ (as scope creeps) could would mean 2 to 10 times more data
(depending on the situation) going back up to the server.
-Josh
On Apr 6, 1:32 pm, Josh wrote:
> I am
ic to support sending
these requests
On Apr 6, 7:41 am, cainlevy wrote:
> "I can agree that its dangerous to destroy attributes in this means,
> but for my case there is no other way"
>
> That's a pretty strong claim. Could you explain a little?
>
> On Ap
Here is the file
http://jibwa.com/samples/dangerous_nested_attributes.rb
here is the article
http://jibwa.com/code-and-documentation-for-programmers/rails-nested-attributes-custom-modific.html
On Apr 5, 6:10 pm, Josh wrote:
> I can agree that its dangerous to destroy attributes in this me
article =>
http://jibwa.com/samples/dangerous_nested_attributes.rb
Here is a link to the file =>http://dangerous_nested_attributes.rb
I'm somewhat new to these groups but if there is some other way I
should share my code with the community, or if I should submit it as a
patch
very large xml data
sets with flex and sending redundant data gets costly and cuts down on
efficiency.
-Josh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to th
It's like the app's schema_migrations
table, but each row has both a version and a plugin name. Migrations
in plugins are accessed by putting a method call in an app migration
that migrates to a particular migration version in the plugin - it's
not automagic, but it works qui
This seems more like a feature addition and less like a bug fix. I'd
say hold off until after the release for it.
--josh
On Mar 11, 2009, at 10:55 AM, Jason King wrote:
>
> Also, this one fixes kind-of a bug:
>
> http://rails.lighthouseapp.com/projects/8994-ruby-on-r
the
correct thing here is to just have activeresource recognize root
elements properly.
Josh Ferguson
On Feb 12, 2009, at 3:20 AM, Frederick Cheung wrote:
>
>
> On 12 Feb 2009, at 08:31, Josh Ferguson wrote:
>>
>> {"account": {"name" : ...}}
ugh I
haven't seen that being generated.
Just a note, I removed all my JSON gems just in case there was some
kind of conflict.
What's going on here, am I just overlooking something?
Josh Ferguson
--~--~-~--~~~---~--~~
You received this message because y
We saw something like this when we had a version of erubis being
required in tucked away corner of one of our initializers, check for
stuff like that as well.
Josh Ferguson
On Jan 31, 2009, at 6:00 PM, Michael Koziarski wrote:
>
>> I'd appreciate any help on how to corr
only way out of this is to move the config.gem stuff into a
separate file that can be used during the environment booting/
initialization, or for building gems without the environment.
--josh
On Jan 23, 2009, at 1:17 PM, Mark Van Holstyn wrote:
> If gems are configured in config/envi
Tiniest patch? I think not!
1 char, plus tests:
http://dev.rubyonrails.org/changeset/7361
:-)
--josh
On Jan 19, 2009, at 1:12 PM, Greg Borenstein wrote:
>
> I just submitted The Tiniest Patch in the World. This patch adds an
> #inspect method to ActiveSupport::OrderedHash to
represents the right concept as a concrete entity.
You should now take this to rubyonrails-t...@googlegroups.com
cheers,
--josh
On Jan 15, 2009, at 12:47 AM, DJ wrote:
>
> Hi
>Group Members
>I am trying to show check-boxes along with
> their state in
th how the Merb form generator does things. Maybe
it's time for a look.
--
Josh Susser
http://blog.hasmanythrough.com
On Dec 26, 2008, at 3:56 AM, Frederick Cheung wrote:
> The form helpers by default wrap fields with errors in a div with an
> appropriate class. Unfortunately this m
have issue with Core Linux
> Administration.
>
> Thanks,
> DeployD.
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
's
great to see even a rough number of the people who've done so much for
Rails.
--josh
On Oct 27, 2008, at 9:41 AM, Xavier Noria wrote:
>
> 2nd version.
>
> Counters have changed and grand total now is ~1400 people!
>
> http://pastie.org/301335
>
> Awesome!
>
array of Comment objects."
This is why I don't like overloading the comments= setter to handle
hashes, but prefer having a comments_params= setter instead. The
basic setter deals with models, the params setter is the convenience
interface for cont
accessors
>>> for create vs update. It's nice and clean, but really any way that
>>> lets you tell create vs update is fine by me.
>
> I'm sorry, but my English is not good enough to follow this bit.
> Could you maybe explain it some
this works much better than trying to
delete records that just happen to be missing from the hash, since
that can get ugly if you are paginating a bunch of records or
otherwise subsetting e the list.
And I do think the _params (or _attributes) suffix on the name is
important.
Anyway, I'l
really any way that
lets you tell create vs update is fine by me.
--josh
On Sep 16, 2008, at 11:27 AM, Ryan Bates wrote:
>
> Cool, Dave, nice approach. I added it to the gist.
> http://gist.github.com/10793
>
> Out of curiosity, do you have a "new task" link on th
I like this feature too, but agree that it wasn't ready for prime time
yet. I just put up a patch for my own take on how to do this. It's
not the whole story, but I wanted to get it up there so we can talk
about it:
http://rails.lighthouseapp.com/projects/8994/tickets/1031
--
Josh S
orters off off. Might be useful in conjunction with named_scopes.
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to
74s
.
Finished in 1.067615 seconds.
2 tests, 2 assertions, 0 failures, 0 errors
If you use some other db than mysql, just change the -I option to use
the correct connection file.
RUNNING_UNIT_TESTS needs updating. I was going to do that at one
point but got distr
On Aug 19, 2008, at 4:58 AM, Chris Cruft wrote:
> The scenario that you mention is a classic one of empty strings being
> returned from forms. And the problem is
> bigger than just booleans. It also applies to strings, numbers and
> lists.
>
> In the scenario Josh mention
g (sorry, Pratik).
To summarize:
I propose that all blank strings should be coerced to nil, for both
boolean and integer fields. Any issues with that? Anyone know if
they are relying on that behavior?
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~--
uild_task(task_params)
p.save
There's a lot that would need to happen to make that example work, and
maybe that's even reaching a bit too far. Anyway, just thinking out
loud.
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~---~--~~
You r
f splitting the setters into two pieces for create and
update. The one thing that keeps bugging me though is doing deletes -
I've still yet to figure out a really nice way to handle that.
--josh
>
>
> Ryan
>
>
> On Jul 17, 4:41 pm, David Dollar <[EMAIL PROTECTED
d_scope is the renamed and integrated-to-core port of
has_finder.
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post to this
Not sure how this would work since we have a gem for each component
and all the components are in one git repo. We might have to split up
them up into different repos.
But it would be cool for people to track rails edge through gems.
On Apr 25, 1:08 pm, Trevor Turk <[EMAIL PROTECTED]> wrote:
> N
I think you're getting a little ahead of yourself. We still haven't
made any real decisions about the direction of ActiveModel. Its pretty
experimental at this point.
Please feel free to continue to play around but don't assume we are
going be taking your direction.
Also, I think we are going go
You're doing a better job than I would of. You know what you want from
the connection pool to do the JRuby voodoo you were talking about.
That makes you more qualified ;)
On Apr 21, 12:07 pm, "Nick Sieger" <[EMAIL PROTECTED]> wrote:
> On Sun, Apr 20, 2008 at 10:17 PM, Jos
Fucking Awesome!
Now what the hell am I going to work on for GSoC? O yeah, AP is still
full of cruft.
On Apr 20, 11:37 am, "Nick Sieger" <[EMAIL PROTECTED]> wrote:
> I've started a refactoring working towards creating a proper
> connection pool class/object for ActiveRecord. Progress can be foun
The sortable_element helper should really be a plugin.
On Apr 15, 12:26 pm, Michal Kwiatkowski <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> Please review and hopefully commit:
>
> Format option of sortable_element helper should accept
> regexpes:http://dev.rubyonrails.org/ticket/11499
>
> sortable_eleme
g pull requests to
> others?
That rails inbox is going be full of shit in no time. Don't bother.
We'll turn off that pull request button on "rails/rails" once it can
be done in Github.
However, I wouldn't mind taking 'tiny' patches in via 'josh/rails',
On Apr 14, 10:35 am, coderrr <[EMAIL PROTECTED]> wrote:
> I agree, mutexes are not the solution for every threading problem, but
> I believe for some problems they are the best (most pragmatic)
> solution. There is a non mutex solution to this race condition which
> is to use a unique method name
On Apr 14, 10:35 am, coderrr <[EMAIL PROTECTED]> wrote:
> I agree, mutexes are not the solution for every threading problem, but
> I believe for some problems they are the best (most pragmatic)
> solution. There is a non mutex solution to this race condition which
> is to use a unique method name
I have my thread safe branch setup already. I'm just toying around w/
some ideas right now. I'll actually start working on it when this
Google Code thing kicks off.
http://github.com/josh/rails/commits/thread_safe
On Apr 11, 10:55 pm, "Michael Koziarski" <[EMAIL PROT
n the spirit they are intended. All
of us in this community make proposals that get shot down for various
reasons, and not everyone disagrees with everyone else on everything.
But when people take the time to respond to you and offer well-
intentioned constructive criticism, it's usu
t syntax that adds methods to Symbol for SQL
operations (e.g. ":foo.not => nil".
This issue has been discussed literally for years. If you want to
play in an open source project like Rails, it's best to do your
homework and check out the other approaches people are u
others. What do
> you think?
If you're jumping in on fixtures, can you take a look at supporting
fixture_scenarios in your changes? If you need help with that, let me
know - I'm motivated to make sure they keep working. From what I've
seen in the fixture_sc
r own attributes. For
that reason, I don't think this is useful as a general way to compact
the XML output. There's also the issue of how to parse the incoming
XML, and how to distinguish between the two XML formats. Removing
unnecessary white space is probably the simplest th
ema.rb
reflects the state of the dev db, you need to know that migrations
have been run correctly. I'm working on a plugin that helps detect
when you need to run migrations, even detecting when someone may have
modified an old
On Feb 17, 10:44 pm, "Michael Koziarski" <[EMAIL PROTECTED]>
wrote:
> I'm prepared to say I'm missing something, but from where I sit ut's
> an interesting idea, but I don't see what we'd get over the current
> use of cgi.rb?
We'd gain support for other adapters, however, I don't really care
that
x27;re using Rack for Merb (1). I
especially like the cascading dispatchers.
1)
http://brainspl.at/articles/2008/02/16/so-merb-core-is-built-on-rack-you-say-why-should-i-care
--
Josh Knowles
phone: 509-979-1593
email: [EMAIL PROTECTED]
web:http://joshknowles.com
--~--~-~--~~--
Has anyone looked into including Rack in Rails? Most of the other web
frameworks seem to be onboard with it (Merb, err).
http://rack.rubyforge.org/
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Cor
ization plugin authors are currently working on a
unified solution that is based on existing plugins.
In the mean time, check out Matt Aimonetti's globalite plugin. It
sounds like it does everything you need.
http://code.google.com/p/globalite/
--
Josh Susser
http://blog.hasmanythro
On 2/13/08, Nuno Job <[EMAIL PROTECTED]> wrote:
>
> I'm Portuguese and it really bothers me that rails has no decent
> internationalization support in it's core.
Last I checked the project was still Open Source, and in fact its
still accepting patches! Feel free to add this functionality if it
r
The new Ruby OpenID library has been released and it has a bunch of
major changes from 1.x.x. This patch updates the OpenIdAuthentication
plugin to use the 2.x.x version.
I wouldn't usually feel much pressure to upgrade, however the ruby-
openid 1.x.x gem is broken after Ruby Gems 1.0 was release
On Dec 19, 10:24 pm, Lawrence Pit <[EMAIL PROTECTED]> wrote:
> 3) A default is arbitrary anyways, so I'd say, let's be a fascist all
> the way: sqlite3. period.
>
> 4) Having one default for all systems means: less code (all 3 lines of
> those ;), less documentation, less confusion.
>
> I'm for mi
nto that problem before now either. Some stuff has changed in AR
that might have affected performance of the select_all approach since
I tried it last, so it might be worth revisiting now.
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~---~--~~
comments, then attach the Verified keyword. You can fish for
collaborators in #rails-contrib on IRC
(irc://irc.freenode.net/rails-contrib) and the rubyonrails-core
mailing list (http://groups.google.com/group/rubyonrails-core).
--
Josh Knowles
phone: 509-979-1593
email: [EMAIL PR
ptimization, which is the rationale? Wouldn't be easier to
> let db:reset run migrations?
This has been discussed quite a bit on this list already, please check
out the archives for the back-story. In the mean time please use rake
db:migrate:reset (included in 2.0.2) to get the functionali
LOL, thank you Mislav.
On Dec 19, 9:38 am, "Mislav Marohnić" <[EMAIL PROTECTED]>
wrote:
> On Dec 19, 2007 4:12 PM, Josh Peek <[EMAIL PROTECTED]> wrote:
>
>
>
> > Either way, I think its fine because rake rails:update asks you if you
> > want to ove
If you are using a more bleeding edge version of prototype (and
friends), rake rails:update will over write them. Or if you've done
crazy stuff to your boot file (even know the doc says not too).
Either way, I think its fine because rake rails:update asks you if you
want to over write any files.
to get information on
how this works, the -talk list is the place to go.
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails: Core" group.
To post
In the meantime, this seems to work:
gem install rails --source http://gems.rubyonrails.org
--
Josh Susser
http://blog.hasmanythrough.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Ruby
on Rails:
1 - 100 of 248 matches
Mail list logo
