[Rails-core] Sexy nayan photos ,videos, stills ,wallpapers

Sexy nayan photos ,videos, stills ,wallpapers http://www.funny-games2all.page.tl/ --~--~-~--~~~---~--~~ 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

[Rails-core] مقطع فيديو [الولاده القي صريه] يمنع دخول ضعاف القلوب

برنامج VMware Workstation 6.0 http://www.antya7la.com/vb/t26858.html#post286993 برنامج يعالج فيروسات auto run و folder option http://www.antya7la.com/vb/t26859.html#post286996 ضع صورتك داخل هذة الساعة http://www.antya7la.com/vb/t26860.html#post286997 زيد سرعة ال Ftp ؟ 64 % + الطريقة مضمونة و

[Rails-core] Re: Out with database.yml

> Please, for the sake of sanity, do not change this from the old way unless > you have a better reason than "It's DRYer" I think that's a perfectly valid reason. Not just that it's more dry, but that it unifies configuration of the database along side the configuration of everything else. The sp

[Rails-core] Re: Out with database.yml

On Wed, Jun 11, 2008 at 06:22:52PM -0700, Scott Bronson wrote: > > On Wed, Jun 11, 2008 at 5:58 PM, Matt Palmer <[EMAIL PROTECTED]> wrote: > > If anything, this patch is anti-DRY because it locks up the database config > > in a place that can only be read by Rails... > > The beauty of this patch

[Rails-core] Re: Out with database.yml

- 1 How about we store the configuration in a c program, which rails has to compile and then execute in order to read the correct data? What I'm trying to say is that this process doesn't seem dryer at all. The YAML file has become the standard and many, many tutorials reference this. Do you not

[Rails-core] Re: Out with database.yml

On Wed, Jun 11, 2008 at 6:22 PM, Scott Bronson <[EMAIL PROTECTED]> wrote: > And it's just as easy to store your database config in XML, CSV, LDAP, > or another database. Your deployment options are wide open. Really, > this patch frees the database config. Where's the downside? Because then it

[Rails-core] Re: Out with database.yml

On Wed, Jun 11, 2008 at 5:58 PM, Matt Palmer <[EMAIL PROTECTED]> wrote: > If anything, this patch is anti-DRY because it locks up the database config > in a place that can only be read by Rails... The beauty of this patch is that now the database config can be read from anywhere. If you still wa

[Rails-core] Re: Out with database.yml

On Wed, Jun 11, 2008 at 5:58 PM, Matt Palmer <[EMAIL PROTECTED]> wrote: > If anything, this patch is anti-DRY because it locks up the database config > in a place that can only be read by Rails. If you've got anything other > than Rails that wants to talk to the database (cron jobs, other apps, >

[Rails-core] Re: Out with database.yml

On Wed, Jun 11, 2008 at 02:16:13PM -0700, Scott Bronson wrote: > > On Wed, Jun 11, 2008 at 9:55 AM, Ben Munat <[EMAIL PROTECTED]> wrote: > > However, the main benefit of switching to a Ruby config file seems to be > > "because database.yml was the only yaml config file", which doesn't seem > > li

[Rails-core] Re: Out with database.yml

On Wed, Jun 11, 2008 at 12:08:42PM -0500, Adam Keys wrote: > As the name of the patch implies, this approach is also considerably > DRYer. If you want, you can define everything in environment.rb and > move on. I'm not sure how you're repeating yourself by putting the database config in a sep

[Rails-core] Re: Where is the ActiveRecord Oracle Adapter with 2.1?

On Wed, Jun 11, 2008 at 11:45 AM, SandroDS <[EMAIL PROTECTED]> wrote: > > I was having the same problem. Then I added the --source option. > Now I'm getting: > > ERROR: While executing gem ... (NoMethodError) >undefined method `gems' for "\037\213\b":String > > Any ideas? * Try it on a diffe

[Rails-core] Re: Out with database.yml

On Wed, Jun 11, 2008 at 9:55 AM, Ben Munat <[EMAIL PROTECTED]> wrote: > However, the main benefit of switching to a Ruby config file seems to be > "because database.yml was the only yaml config file", which doesn't seem > like a particularly great reason. That sounds like a great reason to me. W

[Rails-core] Re: Where is the ActiveRecord Oracle Adapter with 2.1?

I was having the same problem. Then I added the --source option. Now I'm getting: ERROR: While executing gem ... (NoMethodError) undefined method `gems' for "\037\213\b":String Any ideas? On Jun 5, 3:30 am, Michael Schoen <[EMAIL PROTECTED]> wrote: > Please try again, it's working now. > >

[Rails-core] Re: Out with database.yml

On Jun 11, 2008, at 11:55 AM, Ben Munat wrote: > > On the other hand, I like this just because I find the Ruby syntax > more > clearly indicates what you are doing, whereas the yaml is pure data > that > is sucked up into some mysterious place inside Rails. So I guess > that's > more than a

[Rails-core] Re: Out with database.yml

On Jun 11, 2008, at 11:41 AM, Mislav Marohnić wrote: > But I'm worried what about new users? This pratice encourages them > to version their passwords. Rails is opinionated and we have to > choose which practice we will encourage. Will it be database info in > ruby or YAML? > I don't think

[Rails-core] Re: Out with database.yml

Mislav Marohnić wrote: > On Wed, Jun 11, 2008 at 17:04, Adam Keys <[EMAIL PROTECTED] > > wrote: > > > Or you can stick with database.yml :) > > > I will stick with yml for sure and I guess most of experienced devs will > also keep their copies because, now that

[Rails-core] Re: Out with database.yml

On Wed, Jun 11, 2008 at 17:04, Adam Keys <[EMAIL PROTECTED]> wrote: > > Or you can stick with database.yml :) I will stick with yml for sure and I guess most of experienced devs will also keep their copies because, now that we have deployment set up, there is no compelling reason for us to switc

[Rails-core] Query Building in ActiveRecord issues

Hello everyone, I am building an ActiveRecord database adapter for a column store, open source DBMS. When running the calculations_test unit test the following query is generated : SELECT COUNT(*) AS count_all FROM (SELECT DISTINCT "accounts".id FROM "accounts" LEFT OUTER JOIN "companies" ON "

[Rails-core] Re: Out with database.yml

On Jun 11, 2008, at 9:12 AM, Mislav Marohnić wrote: > What I like with database.yml is that I don't version it and > therefore I don't keep production passwords in version control. Also > I can have one database in production locally and another on the > remote machine. > I've done that t

[Rails-core] Re: Out with database.yml

What I like with database.yml is that I don't version it and therefore I don't keep production passwords in version control. Also I can have one database in production locally and another on the remote machine. On Wed, Jun 11, 2008 at 15:39, Adam Keys <[EMAIL PROTECTED]> wrote: > > In short: With

[Rails-core] Out with database.yml

In short: With the help of the friendly folks in #rails-contrib, I've been working on a patch that provides Ruby configuration of your database connections. I'm looking for people to test the patch and post +1s if it works for them. You can find the patch in Lighthouse: http://rails.lightho

[Rails-core] FREE Tutorials on HTML XHTML CSS JavaScript XML XSL ASP SQL ADO VBScript, SAP - ABAP and more...

access all computer tutorials for free visit http://freecomputertutorialz1.blogspot.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-