Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is a Perl script. Right?</p> <p>Why not let Perl figure out what 24 hours earlier time wise is, and then use <code>Time::Piece</code> to parse the Subversion dates?</p> <p>In fact, why are you using <code>svn info</code> and not simply <code>svn log --xml</code>. That will give you the history of all the changes, and you merely have to look at each date and see if it matches your older date.</p> <p>To get the time from 24 hours before, you can use this:</p> <pre><code>use Time::Piece use Time::Seconds #Constants that come in handy my $current_time = localtime; my $yesterday_time = $current_time - ONE_DAY; </code></pre> <p>Now, <code>$yesterday_time</code> is 24 hours before.</p> <p>If you use <code>XML::Simple</code>, you can get the format of the <code>svn log --xml $file</code> output into a handy structure. Here's a simple test program I wrote:</p> <pre class="lang-perl prettyprint-override"><code>#! /usr/bin/perl use strict; use warnings; use autodie; use feature qw(say); use XML::Simple qw(xml_in xml_out); use Time::Piece; use Time::Seconds; my $file_name = "?Some Name?"; my $now = localtime; my $yesterday_time = $now - ONE_DAY; open (my $xml_file, "-|", qq(svn log --xml "$file_name")); my $xml = xml_in($xml_file); # XML is a reference to a hash with a single key 'logentry' # This points to a reference to an array and each entry is # a reference to a hash that contains the four pieces to the # log entry. my $entries_ref = $xml-&gt;{logentry}; foreach my $entry (@{$entries_ref}) { # Each entry is a reference to a hash my $revision = $entry-&gt;{revision}; my $author = $entry-&gt;{author}; my $date = $entry-&gt;{date}; my $message = $entry-&gt;{msg}; # For giggles, we print out the four items. # In truth, there could be more than four items # in the hash if there was also a revprop too. say "$revision: $author: $date: $message"; # The date is in 100,000 of a second. We need to get # rid of everything on the other side of the seconds # decimal before we manipulate it. $date =~ s/\.\d+Z$//; # Get rid of 10,000 of seconds # Now, we can convert the "svn log" date to a Time::Piece my $rev_date = Time::Piece-&gt;strptime($date, "%Y-%m-%dT%H:%M:%S"); # Compare the rev date to the $yesterday_time date if ($rev_date &lt; $yesterday_time) { say "Revision $revision is older than one day" } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POIs there a command using svn to to show the revisions in the last 24 hours?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid W.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs there a command using svn to to show the revisions in the last 24 hours?
      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. VTAcceptedByOriginator
    1. COYes, it is a perl script
      singulars
      1. PO
      1. USJonny
    2. CO@Jonny That was actually a rhetorical question. You mentioned this was a Perl script in your question. Did the information I give you help? Can you use Perl instead of Subversion to determine whether or not a change is over 24 hours old?
      singulars
      1. PO
      1. USDavid W.
    3. COI have been looking at it for a while, trying to determine if I could work it in. In the long run, I am seeking to color code HTML based on subversion. I want to be implementing logic to check if the subversion date had been modified in the last day, and then adjust the HTML color based on that fact. Also I was using info because log was not giving necessarily giving me all the information i needed
      singulars
      1. PO
      1. USJonny
 

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