[viewvc-dev] Change revision number to integer for subversion?

------=_Part_1417_1311497451.1406048459724
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Is there a reason for me not to change commits.revision to an integer in
ViewVC for use with Subversion?

I know, I know "try it and see and make changes as required" and I will.
But I thought I'd get the opinion from the pros first.

In my group, we currently use CVS and query the ViewVC database directly in
our back-end to find out about the CVS history in a way that is not
possible with CVS itself. We're contemplating a switch to SVN and being
able to make queries where we specify " and revision < yyy " would be very
useful.
   I could use commits.ci_when but the commits.revision provides a finer
granularity as ci_when could have been at the same second.

(I understand that for CVS the revision needs to be a varchar (e.g.
"1.4.2.7") . But I don't think that prohibits it being an integer for SVN
uses.)

Thanks,

Stephen Morton

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4251&dsMessageId=3085610

To unsubscribe from this discussion, e-mail: [[email protected]].
------=_Part_1417_1311497451.1406048459724
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Is there a reason for me not to change comm=
its.revision to an integer in ViewVC for use with Subversion?<br><br></div>=
<div>I know, I know &quot;try it and see and make changes as required&quot;=
 and I will. But I thought I&#39;d get the opinion from the pros first.<br>
</div><div><br></div></div>In my group, we currently use CVS and query the =
ViewVC database directly in our back-end to find out about the CVS history =
in a way that is not possible with CVS itself. We&#39;re contemplating a sw=
itch to SVN and being able to make queries where we specify &quot; and revi=
sion &lt; yyy &quot; would be very useful.<br>
</div><div>=C2=A0=C2=A0 I could use commits.ci_when but the commits.revisio=
n provides a finer granularity as ci_when could have been at the same secon=
d.<br></div><div><br>(I understand that for CVS the revision needs to be a =
varchar (e.g. &quot;1.4.2.7&quot;) . But I don&#39;t think that prohibits i=
t being an integer for SVN uses.)<br>
<br></div><div>Thanks,<br></div><br>Stephen Morton<br><br></div>

------=_Part_1417_1311497451.1406048459724--