You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Andry <an...@inbox.ru> on 2017/07/01 18:45:28 UTC
Re: svn status merges intersected external records into single row
Hello Johan,
Friday, June 30, 2017, 11:20:11 PM, you wrote:
JC> Andrey, you might be able to parse the externals from the "Performing
JC> status on external ..." lines as a workaround.
It would be excessive that way. Better just to read the EXTERNALS
table from the wc.db directly.
--
Best regards,
Andry mailto:andry@inbox.ru
Re: svn status merges intersected external records into single row
Posted by Andry <an...@inbox.ru>.
Hello Daniel,
Sunday, July 2, 2017, 7:08:00 AM, you wrote:
DS> Andry wrote on Sat, 01 Jul 2017 21:45 +0300:
>> Hello Johan,
>>
>> Friday, June 30, 2017, 11:20:11 PM, you wrote:
>>
>> JC> Andrey, you might be able to parse the externals from the "Performing
>> JC> status on external ..." lines as a workaround.
>> It would be excessive that way. Better just to read the EXTERNALS
>> table from the wc.db directly.
DS> The db schema may change arbitrarily between versions. If you insist
DS> on this approach, the right way to do it is to check `pragma user_version;`
DS> first and bail out if it's a newer value than your code knows how to handle.
Yes i know, thanx for the tip
--
Best regards,
Andry mailto:andry@inbox.ru
Re: svn status merges intersected external records into single row
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Andry wrote on Sat, 01 Jul 2017 21:45 +0300:
> Hello Johan,
>
> Friday, June 30, 2017, 11:20:11 PM, you wrote:
>
> JC> Andrey, you might be able to parse the externals from the "Performing
> JC> status on external ..." lines as a workaround.
> It would be excessive that way. Better just to read the EXTERNALS
> table from the wc.db directly.
The db schema may change arbitrarily between versions. If you insist
on this approach, the right way to do it is to check `pragma user_version;`
first and bail out if it's a newer value than your code knows how to handle.
The public API is what Johan suggested, or to use the libsvn_client bindings
in the language of your choice (C/java/python/perl/ruby).