Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Newer versions of Ruby (2.0+) do not really have significant differences between the two classes. Some libraries will use one or the other for historical reasons, but new code does not necessarily need to be concerned. Picking one for consistency is probably best, so try and mesh with what your libraries expect. For example, ActiveRecord prefers DateTime.</p> <p>In versions prior to Ruby 1.9 and on many systems Time is represented as a 32-bit signed value describing the number of seconds since January 1, 1970 UTC, a thin wrapper around a POSIX-standard <code>time_t</code> value, and is bounded:</p> <pre><code>Time.at(0x7FFFFFFF) # =&gt; Mon Jan 18 22:14:07 -0500 2038 Time.at(-0x7FFFFFFF) # =&gt; Fri Dec 13 15:45:53 -0500 1901 </code></pre> <p>Newer versions of Ruby are able to handle larger values without producing errors.</p> <p>DateTime is a calendar-based approach where the year, month, day, hour, minute and second are stored individually. This is a Ruby on Rails construct that serves as a wrapper around SQL-standard DATETIME fields. These contain arbitrary dates and can represent nearly any point in time as the range of expression is typically very large.</p> <pre><code>DateTime.new # =&gt; Mon, 01 Jan -4712 00:00:00 +0000 </code></pre> <p>So it's reassuring that DateTime can handle blog posts from Aristotle.</p> <p>When choosing one, the differences are somewhat subjective now. Historically DateTime has provided better options for manipulating it in a calendar fashion, but many of these methods have been ported over to Time as well, at least within the Rails environment.</p>
    singulars
    1. This table or related slice is empty.
    1. PODifference between DateTime and Time in Ruby
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UStadman
    1. UStadman
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PODifference between DateTime and Time in Ruby
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo should I always use DateTime?
      singulars
      1. PO
      1. USTom Lehman
    2. COIf you're working with dates, I'd say use DateTime. Time is convenient for representing things such as current time of day, or points in the near future such as 10.minutes.from_now. The two have a lot in common, though as noted DateTime can represent a much wider range of values.
      singulars
      1. PO
      1. UStadman
    3. CO> Time is convenient for representing things such as current time of day, or points in the near future such as 10.minutes.from_now. Why is Time more convenient than DateTime for this purpose?
      singulars
      1. PO
      1. USTom Lehman
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload