Re: [Rails-core] [3795] render_component doesn't work with modules?

2006-02-11 Thread Stefan Kaes
Rick Olson wrote: On 2/10/06, Trevor Squires <[EMAIL PROTECTED]> wrote: Hi Nathaniel, I'm using a version of edge (not the most recent, but after module namespace support was improved) and I use render_component into a module namespace quite extensively with no problems. I know you said you

RE: [Rails-core] AR Unit Tests

2006-02-11 Thread Bob Silva
Hi Wilson, The problem was with the comment in front of the table. In MySQL, comments starting with -- need a whitespace character following it. Bob Silva http://www.railtie.net/ > -Original Message- > From: [EMAIL PROTECTED] [mailto:rails-core- > [EMAIL PROTECTED] On Behalf Of Wilson Bi

RE: [Rails-core] Date Helper Mega Patch

2006-02-11 Thread Bob Silva
The current way I'm planning on implementing this is to have hidden text fields for the date components. The only database this doesn't work with is SQLite since it won't convert the datetime into a time upon save. Haven't checked to see if there was a hook to convert the Time object into a time st

Re: [Rails-core] Multithreaded script/runner

2006-02-11 Thread Greg Lappen
Hi Tom, Thanks for the update. Have you heard anything about getting this code committed into subversion? On Feb 10, 2006, at 5:24 AM, Tom Ward wrote: I've been using the pooled adapter on some installations without any obvious problems, but not running against rails 1.0. I know that som

Re: [Rails-core] AR Unit Tests

2006-02-11 Thread Wilson Bilkovich
Good to know. I'll be more careful with when guessing at MySQL syntax next time. Sorry for the inconvenience. :) On 2/11/06, Bob Silva <[EMAIL PROTECTED]> wrote: > Hi Wilson, > > The problem was with the comment in front of the table. In MySQL, comments > starting with -- need a whitespace charact

Re: [Rails-core] anyone in a committing mood?

2006-02-11 Thread Blair Zajac
On Feb 10, 2006, at 11:49 AM, David Heinemeier Hansson wrote: If it would help I can bundle them all up into a single patch, just let me know. It would. Please do roll them all up into 1 patch and get a few Oracle'ers to try that out. If you could get them to comment on this new ticket with

[Rails-core] Default <%= to use the h (html safe) method.

2006-02-11 Thread Nathaniel S. H. Brown
I was just reading a blog post, about how PHP applications lack so much as far as security goes, and it got me thinking that Rails should come default secure, and you should have to force it to be less secure. On that note, I came up with the idea of having <%= default to use the XSS safe (or soon

Re: [Rails-core] Default <%= to use the h (html safe) method.

2006-02-11 Thread Michael Koziarski
On 2/12/06, Nathaniel S. H. Brown <[EMAIL PROTECTED]> wrote: > I was just reading a blog post, about how PHP applications lack so much as > far as security goes, and it got me thinking that Rails should come default > secure, and you should have to force it to be less secure. > > On that note, I ca

Re: [Rails-core] Default <%= to use the h (html safe) method.

2006-02-11 Thread Obie Fernandez
+1 Would reduce clutter on the templates. It's pretty annoying to have to remember to put them in, and even more annoying to get tickets from QA about XSS. On 2/11/06, Nathaniel S. H. Brown <[EMAIL PROTECTED]> wrote: > I was just reading a blog post, about how PHP applications lack so much as > f

RE: [Rails-core] Default <%= to use the h (html safe) method.

2006-02-11 Thread Nathaniel S. H. Brown
Good point. We could always make it a configuration option for 1.0? -Nb ~ Nathaniel S. H. Brown http://nshb.net ~ > -Original Message

Re: [Rails-core] Default <%= to use the h (html safe) method.

2006-02-11 Thread Tobias Luetke
huh? that would break url_for, link_to, textilize, markdown and every single other helper which outputs html tags. I use the h helper in like 3 different places in shopify, thats definitely the exception. > On that note, I came up with the idea of having <%= default to use the XSS > safe (or soon

RE: [Rails-core] Default <%= to use the h (html safe) method.

2006-02-11 Thread Nathaniel S. H. Brown
All of those helper functions would obviously need to be changed so that they work with the default <%=h methods. The <%= tag could be smart enough to realize what it is parsing, and if it's a helper method, to skip it. It's an abstract idea. If it's worth investigating, we can look at how to impl

Re: [Rails-core] Default <%= to use the h (html safe) method.

2006-02-11 Thread Michael Koziarski
On 2/12/06, Nathaniel S. H. Brown <[EMAIL PROTECTED]> wrote: > All of those helper functions would obviously need to be changed so that > they work with the default <%=h methods. The <%= tag could be smart enough > to realize what it is parsing, and if it's a helper method, to skip it. > > It's an

Re: [Rails-core] Default <%= to use the h (html safe) method.

2006-02-11 Thread Stefan Kaes
Nathaniel S. H. Brown wrote: I was just reading a blog post, about how PHP applications lack so much as far as security goes, and it got me thinking that Rails should come default secure, and you should have to force it to be less secure. On that note, I came up with the idea of having <%= defau

[Rails-core] select_datetime

2006-02-11 Thread Bob Silva
Hi guys, Spent most of the day rewriting date_helper to close all the open tickets against it. Was just making sure everything was tested when I noticed that select_datetime doesn't use the dash between the date and time, nor : for the time components. Ditto on the select_time method. Would it be