thr3ads.net - Rails - Differences in execution between console and app [Oct 2007]

If this information is useful, please help other people find it:
Share via:

Daniel Waite

2007-Oct-07 18:24 UTC

Differences in execution between console and app

class AppointmentBook < ActiveRecord::Base

  has_many :appointments

  def lookup(date, look_ahead = 27)
    return nil unless block_given?

    (date..date + look_ahead).each do |date|
      yield(date, appointments.find_all_by_date(date))
    end
  end

end

The line with yield is throwing the error:
undefined method ''each'' for #<Date: 4908761/2,0,2299161>

A YAML dump of date yields:>>> DATE: --- 2007-10-07 (CLASS: Date)
However, a very similar line of code works fine in console:
appointment_book.appointments.find_all_by_date(Date.today) # []

The empty array is expected.

The kicker: if I call #to_s on date inside my method, it works. But I
shouldn''t have to call #to_s.

Any ideas?
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Rick DeNatale

2007-Oct-07 19:45 UTC

head link

Re: Differences in execution between console and app

On 10/7/07, Daniel Waite
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
> class AppointmentBook < ActiveRecord::Base
>
>   has_many :appointments
>
>   def lookup(date, look_ahead = 27)
>     return nil unless block_given?
>
>     (date..date + look_ahead).each do |date|
>       yield(date, appointments.find_all_by_date(date))
>     end
>   end
>
> end

> The line with yield is throwing the error:
> undefined method ''each'' for #<Date:
4908761/2,0,2299161>
What do you EXPECT this to do?

Assuming that date is a Date then date+lookahead is also going to be a Date.

Dates aren''t enumerable, and don''t have an each method.

If you want this to yield each appointment with a date look_ahead days
from date, then you probably want something like:

  def lookup(date, look_ahead = 27)
    return nil unless block_given?

     appointments.find_all_by_date(date..date + look_ahead).each do
|appointment|
        yield appointment
     end
   end
> The kicker: if I call #to_s on date inside my method, it works. But I
> shouldn''t have to call #to_s.
to_s will return a string representation of the date. Strings DO have
an each method which when called without an argument yields each "\n"
delimited line in the string.

-- 
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 20:03 UTC

head link

Re: Differences in execution between console and app

Rick Denatale wrote:> What do you EXPECT this to do?
Return an array.
> Assuming that date is a Date then date+lookahead is also going to be a 
> Date.
> 
> Dates aren''t enumerable, and don''t have an each method.
True, Dates are not enumerable, but ranges are, and they respond to 
each:

(date..date + look_ahead).class # Range
(date..date + look_ahead).respond_to? :each # true
> If you want this to yield each appointment with a date look_ahead days
> from date, then you probably want something like:
> 
>   def lookup(date, look_ahead = 27)
>     return nil unless block_given?
> 
>      appointments.find_all_by_date(date..date + look_ahead).each do
> |appointment|
>         yield appointment
>      end
>    end
That achieves a similar effect, but I want my appointments to be grouped 
by date. True there are other ways to group by date, but it makes my 
views easier if I get a date and a collection of appointments on that 
date. View:

<% @tattoo_artist.appointment_book.lookup(@date) do |date, appointments| 
%>
  <div class="appointment">
    <h1><%= date.strftime(''%A'') %><%=
'' (Today)'' if
date.eql?(Date.today) %></h1>
    <h2><%= date.strftime(''%B %d, %Y'')
%></h2>
    <% appointments.each do |appointment| %>
      <p><strong><%= appointment.time %> with <%= 
appointment.client.name %></strong><br /><%=
appointment.description
%></p>
    <% end %>
  </div>
<% end %>

In other words, I want:

Date
  Appointment for that date
  Appointment for that date
  Appointment for that date
Date
  Appointment for that date

Even if I were to use SQL to group the results by date, I''d have to 
perform extra manipulation to get the above effect. In this case I 
prefer cleanliness over efficiency.
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

atpunkt-TM7Dk29TcfyELgA04lAiVw@public.gmane.org

2007-Oct-07 20:08 UTC

head link

Re: Differences in execution between console and app

You can''t create a Range over 2 Dates and iterate over those -
I''m
assuming that''s what you want to do.

but what you can do is iterate over the lookahead

(0..look_ahead).each do |diff|
  yield (date+diff.....)
end

On 7 Okt., 20:24, Daniel Waite
<rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:> class AppointmentBook < ActiveRecord::Base
>
>   has_many :appointments
>
>   def lookup(date, look_ahead = 27)
>     return nil unless block_given?
>
>     (date..date + look_ahead).each do |date|
>       yield(date, appointments.find_all_by_date(date))
>     end
>   end
>
> end
>
> The line with yield is throwing the error:
> undefined method ''each'' for #<Date:
4908761/2,0,2299161>
>
> A YAML dump of date yields:
>
> >>> DATE: --- 2007-10-07 (CLASS: Date)
>
> However, a very similar line of code works fine in console:
> appointment_book.appointments.find_all_by_date(Date.today) # []
>
> The empty array is expected.
>
> The kicker: if I call #to_s on date inside my method, it works. But I
> shouldn''t have to call #to_s.
>
> Any ideas?
> --
> Posted viahttp://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 20:11 UTC

head link

Re: Differences in execution between console and app

atpunkt-TM7Dk29TcfyELgA04lAiVw@public.gmane.org wrote:> You can''t create a Range over 2 Dates and iterate over those -
I''m
> assuming that''s what you want to do.
>> (Date.today..Date.today + 10).each do |date| 
?>   puts date>> end2007-10-07
2007-10-08
2007-10-09
2007-10-10
2007-10-11
2007-10-12
2007-10-13
2007-10-14
2007-10-15
2007-10-16
2007-10-17
=> #<Date: 4908761/2,0,2299161>..#<Date: 4908781/2,0,2299161>

-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 20:19 UTC

head link

Re: Differences in execution between console and app

atpunkt-TM7Dk29TcfyELgA04lAiVw@public.gmane.org wrote:> You can''t create a Range over 2 Dates and iterate over those -
I''m
> assuming that''s what you want to do.
> 
> but what you can do is iterate over the lookahead
> 
> (0..look_ahead).each do |diff|
>   yield (date+diff.....)
> end
I think we''ve gotten a little off-track. Allow me to steer us back in 
the right direction...

This is the line throwing the error in my app:

appointments.find_all_by_date(date)

In console, that same line works fine.

I''ve logger.debugged date in my method and it looks like a date.

I''ve even pulled that line out of the yield and made it the first line 
in my method and that line is where it fails:

def lookup(date, look_ahead = 27)
  logger.debug("\n\n>>> DATE: #{ date.class }" # Yup,
it''s a date.
  appointments.find_all_by_date(date) # Dies here now...

  return nil unless block_given?

  (date..date + look_ahead).each do |date|
    yield(date, appointments.find_all_by_date(date)) # ...instead of 
here.
  end
end
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Pat Maddox

2007-Oct-07 20:22 UTC

head link

Re: Differences in execution between console and app

On 10/7/07, Daniel Waite
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
> class AppointmentBook < ActiveRecord::Base
>
>   has_many :appointments
>
>   def lookup(date, look_ahead = 27)
>     return nil unless block_given?
>
>     (date..date + look_ahead).each do |date|
>       yield(date, appointments.find_all_by_date(date))
>     end
>   end
>
> end
>
> The line with yield is throwing the error:
> undefined method ''each'' for #<Date:
4908761/2,0,2299161>
>
> A YAML dump of date yields:
> >>> DATE: --- 2007-10-07 (CLASS: Date)
>
> However, a very similar line of code works fine in console:
> appointment_book.appointments.find_all_by_date(Date.today) # []
>
> The empty array is expected.
>
> The kicker: if I call #to_s on date inside my method, it works. But I
> shouldn''t have to call #to_s.
>
> Any ideas?
> --
> Posted via http://www.ruby-forum.com/.
>
> >
>
It''s not a problem of iterating over the range, cause as
you''ve
pointed out you can iterate over a range of dates.

Looks like it''s either a bug in the client code or maybe something
weird about AR''s #find_all_by...

I would simplify this in order to debug.  First just yield the date
itself and don''t worry about the appointments.  Take out all the
appointment display code.

The other possibility (unlikely though) is some weirdness in
find_all_by like I said.  Try changing the call to
appointments.find(:all, :conditions => ["date=?", Date.today])

but as you can see, you''re iterating through the dates fine. 
There''s
just something strange happening in the code that''s being called via
yield, or perhaps something funky under the hood.

Pat

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

atpunkt-TM7Dk29TcfyELgA04lAiVw@public.gmane.org

2007-Oct-07 20:26 UTC

head link

Re: Differences in execution between console and app

ok i seems you sometimes CAN create ranges of dates - but that it
doesn''t work in a running app points towards some strange view-helpers
being added to the date-class or something like that.
my method should still work, while yours implies some kind of hidden
to_i/to_date back-and-forth which could lead to that error. don''t try
to force it if there is another way.

Phil


On 7 Okt., 22:11, Daniel Waite
<rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:> atpu...-TM7Dk29TcfyELgA04lAiVw@public.gmane.org wrote:
> > You can''t create a Range over 2 Dates and iterate over those
- I''m
> > assuming that''s what you want to do.
> >> (Date.today..Date.today + 10).each do |date|
> ?>   puts date
> >> end
>
> 2007-10-07
> 2007-10-08
> 2007-10-09
> 2007-10-10
> 2007-10-11
> 2007-10-12
> 2007-10-13
> 2007-10-14
> 2007-10-15
> 2007-10-16
> 2007-10-17
> => #<Date: 4908761/2,0,2299161>..#<Date:
4908781/2,0,2299161>
>
> --
> Posted viahttp://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Frederick Cheung

2007-Oct-07 20:28 UTC

head link

Re: Differences in execution between console and app

On 7 Oct 2007, at 21:19, Daniel Waite wrote:
>
> atpunkt-TM7Dk29TcfyELgA04lAiVw@public.gmane.org wrote:
>> You can''t create a Range over 2 Dates and iterate over those -
I''m
>> assuming that''s what you want to do.
>>
>> but what you can do is iterate over the lookahead
>>
>> (0..look_ahead).each do |diff|
>>   yield (date+diff.....)
>> end
>
> I think we''ve gotten a little off-track. Allow me to steer us back
in
> the right direction...
>
> This is the line throwing the error in my app:
>
> appointments.find_all_by_date(date)
>What''s the stack trace of the error?

Fred>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

atpunkt-TM7Dk29TcfyELgA04lAiVw@public.gmane.org

2007-Oct-07 20:37 UTC

head link

Re: Differences in execution between console and app

ah .. yes sorry I seem to be responding while new and  clarifying
messages are added to this thread.. that way I got off-track.

have you tried converting the date to a string before the
find_all_by_date() ?
or formulating it as a :conditions array ?

these are not solutions but you could analyse the problem from
different angles like that.

P


On 7 Okt., 22:19, Daniel Waite
<rails-mailing-l...-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:> atpu...-TM7Dk29TcfyELgA04lAiVw@public.gmane.org wrote:
> > You can''t create a Range over 2 Dates and iterate over those
- I''m
> > assuming that''s what you want to do.
>
> > but what you can do is iterate over the lookahead
>
> > (0..look_ahead).each do |diff|
> >   yield (date+diff.....)
> > end
>
> I think we''ve gotten a little off-track. Allow me to steer us back
in
> the right direction...
>
> This is the line throwing the error in my app:
>
> appointments.find_all_by_date(date)
>
> In console, that same line works fine.
>
> I''ve logger.debugged date in my method and it looks like a date.
>
> I''ve even pulled that line out of the yield and made it the first
line
> in my method and that line is where it fails:
>
> def lookup(date, look_ahead = 27)
>   logger.debug("\n\n>>> DATE: #{ date.class }" # Yup,
it''s a date.
>   appointments.find_all_by_date(date) # Dies here now...
>
>   return nil unless block_given?
>
>   (date..date + look_ahead).each do |date|
>     yield(date, appointments.find_all_by_date(date)) # ...instead of
> here.
>   end
> end
> --
> Posted viahttp://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 20:40 UTC

head link

Re: Differences in execution between console and app

Pat Maddox wrote:> I would simplify this in order to debug.  First just yield the date
> itself and don''t worry about the appointments.  Take out all the
> appointment display code.
> The other possibility (unlikely though) is some weirdness in
> find_all_by like I said.  Try changing the call to
> appointments.find(:all, :conditions => ["date=?", Date.today])
Good suggestions Pat. And the situation gets weirder. I tried specifying 
conditions as you suggested and get the same error.

@atpunkt-TM7Dk29TcfyELgA04lAiVw@public.gmane.org:
I tried iterating through 0..look_ahead and adding the difference to 
date and still get the same error.

Frederick Cheung wrote:> What''s the stack trace of the error?
Stack trace: <a 
href="http://pastie.caboo.se/104710">http://pastie.caboo.se/104710</a>
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 20:40 UTC

head link

Re: Differences in execution between console and app

Daniel Waite wrote:> Frederick Cheung wrote:
>> What''s the stack trace of the error?
> 
> Stack trace: 
http://pastie.caboo.se/104710
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Pat Maddox

2007-Oct-07 20:42 UTC

head link

Re: Differences in execution between console and app

On 10/7/07, Daniel Waite
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
> Pat Maddox wrote:
> > I would simplify this in order to debug.  First just yield the date
> > itself and don''t worry about the appointments.  Take out all
the
> > appointment display code.
>
> > The other possibility (unlikely though) is some weirdness in
> > find_all_by like I said.  Try changing the call to
> > appointments.find(:all, :conditions => ["date=?",
Date.today])
>
> Good suggestions Pat. And the situation gets weirder. I tried specifying
> conditions as you suggested and get the same error.
>
> @atpunkt-TM7Dk29TcfyELgA04lAiVw@public.gmane.org:
> I tried iterating through 0..look_ahead and adding the difference to
> date and still get the same error.
>
> Frederick Cheung wrote:
> > What''s the stack trace of the error?
>
> Stack trace: <a
>
href="http://pastie.caboo.se/104710">http://pastie.caboo.se/104710</a>
Oh, yeah, weird.  I would just change it to
appointments.find_all_by_date Date.today.to_s(:db)

and cross my fingers.

Pat

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Pat Maddox

2007-Oct-07 20:45 UTC

head link

Re: Differences in execution between console and app

On 10/7/07, Daniel Waite
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
> Daniel Waite wrote:
> > Frederick Cheung wrote:
> >> What''s the stack trace of the error?
> >
> > Stack trace:
>
> http://pastie.caboo.se/104710
What database are you using?  Version, and adapter version?  It looks
like AR isn''t treating something as a date there.  Like it''s
sanitizing the SQL as a string...which most likely means (to me) that
for some reason it doesn''t know that the db column is a date.  Did you
perhaps mess up on the migration and create the date field as a string
instead of a date?

Pat

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 20:45 UTC

head link

Re: Differences in execution between console and app

Pat Maddox wrote:> Oh, yeah, weird.  I would just change it to
> appointments.find_all_by_date Date.today.to_s(:db)
> 
> and cross my fingers.
> 
> Pat
What does the (:db) to?
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Frederick Cheung

2007-Oct-07 20:47 UTC

head link

Re: Differences in execution between console and app

On 7 Oct 2007, at 21:45, Daniel Waite wrote:
>
> Pat Maddox wrote:
>> Oh, yeah, weird.  I would just change it to
>> appointments.find_all_by_date Date.today.to_s(:db)
>>
>> and cross my fingers.
>>
>> Pat
>
> What does the (:db) to?
ActiveSupport overrides Date#to_s, passing :db makes it format the  
string in the way the database wants it.
Fred> -- 
> Posted via http://www.ruby-forum.com/.
>
> >

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Rick DeNatale

2007-Oct-07 21:00 UTC

head link

Re: Differences in execution between console and app

On 10/7/07, Daniel Waite
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
> Rick Denatale wrote:
> > What do you EXPECT this to do?
>
> Return an array.
>
> > Assuming that date is a Date then date+lookahead is also going to be a
> > Date.
> >
> > Dates aren''t enumerable, and don''t have an each
method.
>
> True, Dates are not enumerable, but ranges are, and they respond to
> each:
>
> (date..date + look_ahead).class # Range
> (date..date + look_ahead).respond_to? :each # true
Sorry I missed the two dots.

You said it was the line with the yield which is raising the
exception, but there''s no each there.

So...

It would seem to be something called by that line.

Others are looking at the find_all_by date, but what about the block
you are yielding to?  What''s in that block?
-- 
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 21:02 UTC

head link

Re: Differences in execution between console and app

Pat Maddox wrote:> What database are you using?  Version, and adapter version?  It looks
> like AR isn''t treating something as a date there.  Like
it''s
> sanitizing the SQL as a string...which most likely means (to me) that
> for some reason it doesn''t know that the db column is a date.  Did
you
> perhaps mess up on the migration and create the date field as a string
> instead of a date?
MySQL. Not sure what version. I''m on OS 10.4 -- anyone know how to 
check?

I assume I''m using the the mysql gem adapter. gem list:

mysql (2.7)
    MySQL/Ruby provides the same functions for Ruby programs that the
    MySQL C API provides for C programs.

Schema for appointments:

create_table "appointments", :force => true do |t|
  t.column "client_id",           :integer
  t.column "date",                :date
  t.column "time",                :string
  t.column "duration",            :integer
  t.column "appointment_book_id", :integer
  t.column "description",         :text
end

 Frederick Cheung wrote:>> What does the (:db) to?
>ActiveSupport overrides Date#to_s, passing :db makes it format the
> string in the way the database wants it.
Sweet. I didn''t know that; thanks, Fred. :)
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 21:04 UTC

head link

Re: Differences in execution between console and app

Rick Denatale wrote:>>
>> (date..date + look_ahead).class # Range
>> (date..date + look_ahead).respond_to? :each # true
> 
> Sorry I missed the two dots.
No problem. We''re programmers; we miss things everyday. At least I do!
> You said it was the line with the yield which is raising the
> exception, but there''s no each there.
> 
> Others are looking at the find_all_by date, but what about the block
> you are yielding to?  What''s in that block?
It''s not the block. I''ve removed everything from that method
(including
simplifying the caller of the method to exclude passing a block) except 
the find_all_by_xxx and it still errors out.
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Rick DeNatale

2007-Oct-07 21:09 UTC

head link

Re: Differences in execution between console and app

On 10/7/07, Daniel Waite
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
> Rick Denatale wrote:
> >>
> >> (date..date + look_ahead).class # Range
> >> (date..date + look_ahead).respond_to? :each # true
> >
> > Sorry I missed the two dots.
>
> No problem. We''re programmers; we miss things everyday. At least I
do!
>
> > You said it was the line with the yield which is raising the
> > exception, but there''s no each there.
> >
> > Others are looking at the find_all_by date, but what about the block
> > you are yielding to?  What''s in that block?
>
> It''s not the block. I''ve removed everything from that
method (including
> simplifying the caller of the method to exclude passing a block) except
> the find_all_by_xxx and it still errors out.
So what line in what file is actually suffering the method missing?
Seems to be time to take advantage of the fact that ActiveRecord and
the rest of Rails is open source.

-- 
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Pat Maddox

2007-Oct-07 21:11 UTC

head link

Re: Differences in execution between console and app

On 10/7/07, Daniel Waite
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
> Rick Denatale wrote:
> >>
> >> (date..date + look_ahead).class # Range
> >> (date..date + look_ahead).respond_to? :each # true
> >
> > Sorry I missed the two dots.
>
> No problem. We''re programmers; we miss things everyday. At least I
do!
>
> > You said it was the line with the yield which is raising the
> > exception, but there''s no each there.
> >
> > Others are looking at the find_all_by date, but what about the block
> > you are yielding to?  What''s in that block?
>
> It''s not the block. I''ve removed everything from that
method (including
> simplifying the caller of the method to exclude passing a block) except
> the find_all_by_xxx and it still errors out.
> --
> Posted via http://www.ruby-forum.com/.
>
> >
>
Try starting a new project and just build up a little bit.  I did a
new project that used that column name and type, and no error.  So I
thought maybe it was a problem with the association, but that still
worked fine.  Basically I''d put in the absolutely simplest stuff, and
build up to the same structure that you currently have, and see where
it breaks along the way.

Pat

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Daniel Waite

2007-Oct-07 22:47 UTC

head link

Re: Differences in execution between console and app

Rick Denatale wrote:> So what line in what file is actually suffering the method missing?
> Seems to be time to take advantage of the fact that ActiveRecord and
> the rest of Rails is open source.
Aye, that it does.

Pat Maddox wrote:> Try starting a new project and just build up a little bit.
> Basically I''d put in the absolutely simplest stuff, and
> build up to the same structure that you currently have, and
> see where it breaks along the way.
I''ll do that before diving into ActiveRecord, though I fear
that''s where
this may lead.

Thanks everyone for all your help; I appreciate it!
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Rick DeNatale

2007-Oct-08 13:14 UTC

head link

Re: Differences in execution between console and app

On 10/7/07, Daniel Waite
<rails-mailing-list-ARtvInVfO7ksV2N9l4h3zg@public.gmane.org>
wrote:>
> Rick Denatale wrote:
> > So what line in what file is actually suffering the method missing?
> > Seems to be time to take advantage of the fact that ActiveRecord and
> > the rest of Rails is open source.
>
> Aye, that it does.
>
> Pat Maddox wrote:
> > Try starting a new project and just build up a little bit.
> > Basically I''d put in the absolutely simplest stuff, and
> > build up to the same structure that you currently have, and
> > see where it breaks along the way.
>
> I''ll do that before diving into ActiveRecord, though I fear
that''s where
> this may lead.
I find that looking at the source is usually the quickest way to
figure these kind of things out.

The same debugging techniques that you use for your own code work for
library code.

Plus there''s the benefit that you often learn useful things in looking
at the code.

-- 
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denhaven2.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Ruby on Rails: Talk" group.
To post to this group, send email to
rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
To unsubscribe from this group, send email to
rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
For more options, visit this group at
http://groups.google.com/group/rubyonrails-talk?hl=en
-~----------~----~----~----~------~----~------~--~---

Possibly Parallel Threads

Search for more possibly parallel threads

Rails - Oct 2007 - Differences in execution between console and app

Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Re: Differences in execution between console and app

Possibly Parallel Threads