On Dec 27, 2017, at 1:49 PM, Bob Friesenhahn
wrote:
>
> Any DVCS is going to cause a penalty when the goal is to check out a
> particular version of the files from a remote server
…the first time.
After you’ve got a clone, operations are usually much faster with a DVCS than a
remote non-dist
Hi Dan. $ xxd row2.txt
000: 7465 7874 206f 6620 6669 6c65 2072 6f77 text of file row
010: 322e 7478 740a 2.txt.
0a. Normally dependable Gedit, used for such tinkering, is putting in that
linefeed. From my regular IDE I also see it.
Sorry for the possible false
On 27 Dec 2017, at 6:55pm, Simon Slavin wrote:
> An alternative might be to run "integrity_check" on backup copies which don’t
> show up anything on "quick_check". This could be done without blocking the
> production system. If you never find anything then you know "quick_check" is
> all you
Hi,
Many thanks for the very detailed answer, it is of great help
2017-12-26 15:28 GMT+01:00 Dan Kennedy :
> On 12/25/2017 11:17 PM, Josu Diaz de Arcaya wrote:
>
>> Hi all,
>>
>> I am very happy with the inclusion of LSM extension in sqlite3's code
>> base.
>> I have a question regarding
>> the
On Wed, 27 Dec 2017, Simon Slavin wrote:
I understand that ZFS does this too, though I’ve never used ZFS.
ZFS currently clones on the filesystem level. Filesystems are easy to
create/delete and only consume the space required. Once a filesystem
has been cloned, then only modified file bloc
I don’t see what the problem is, do you not expect a newline at the end of the
line in a file?
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On 12/27/17, 2:23 PM, "sqlite-users on behalf of Simon Slavin"
wrote:
> Fair point. Automatic de-duplication would be more beneficial. And it
> wouldn’t require extreme cleverness to be separately written into each
> application. APFS does not do automatic de-duplication.
We had Netapp file
Thanks Richard for the response!
On 12/21/17 5:07 PM, Richard Hipp wrote:
On 12/21/17, Nikhil Deshpande wrote:
There were no power-off or reboots in near time vicinity when the
corruption was detected.
(1) Might the corruption have been sitting dormant due to some far
away power-off or rebo
On 12/28/2017 03:20 AM, petern wrote:
sqlite> load zipfile.so
sqlite> SELECT * FROM zipfile('rows.zip');
name,mode,mtime,sz,data,method
row1.txt,33204,1514396814,22,"text of file row1.txt
",0
row2.txt,33204,1514396416,22,"text of file row2.txt
",0
--Extra newline is introduced for some reason.
On 27 Dec 2017, at 8:20pm, petern wrote:
> --Added explicit newline to end of row1.txt
How. What did you do ? Was it a NL or a CR ? Or done as Unicode ?
Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.s
On 27 Dec 2017, at 8:10pm, Warren Young wrote:
> It is almost certainly the case that some of the files in x and y are
> identical so that those files could be cloned from those in the other at the
> filesystem level by making one of these OS-specific API calls, but it would
> require a lot
sqlite> load zipfile.so
sqlite> SELECT * FROM zipfile('rows.zip');
name,mode,mtime,sz,data,method
row1.txt,33204,1514396814,22,"text of file row1.txt
",0
row2.txt,33204,1514396416,22,"text of file row2.txt
",0
--Extra newline is introduced for some reason.
--Added explicit newline to end of row1.
On Dec 27, 2017, at 11:14 AM, Simon Slavin wrote:
>
> On 27 Dec 2017, at 4:05pm, Warren Young wrote:
>
>> DVCSes...by their very nature...want to clone the entire history of the
>> whole project to every machine, then make a second copy of the tip of each
>> working branch
>
> Apple recently
On 27 Dec 2017, at 6:49pm, Peter Da Silva wrote:
> On 12/27/17, 12:14 PM, "sqlite-users on behalf of Simon Slavin"
> slav...@bigfraud.org> wrote:
>
>> Would running git/fossil on a filesystem like that solve the problem ?
>
> You would have to modify it to use the new APIs for things like cop
On 27 Dec 2017, at 6:10pm, Nikhil Deshpande wrote:
>> Can you include a "pragma integrity_check" at startup ?
>> Can you include a "pragma integrity_check" executed at regular intervals ?
> The writer process does "pragma quick_check" on every startup at init,
> bails out on failure and spawns
On 12/27/17, 12:14 PM, "sqlite-users on behalf of Simon Slavin"
wrote:
> Would running git/fossil on a filesystem like that solve the problem ?
You would have to modify it to use the new APIs for things like copying files.
___
sqlite-users mailing l
On 27 Dec 2017, at 4:05pm, Warren Young wrote:
> Fossil has that problem, too. Most DVCSes do, because by their very nature,
> they want to clone the entire history of the whole project to every machine,
> then make a second copy of the tip of each working branch you check out.
> That’s a
On 12/21/17 9:45 PM, Rowan Worth wrote:
Does either process take backups of the DB? If so, how is that implemented?
Thanks Rowan for the response!
Backup is done by a separate process through command:
sqlite3 /path/to/db_file .dump > dump.sql
and not using the sqlite3 backup API.
Thanks,
N
Thanks Simon for the response!
On 12/21/17 5:05 PM, Simon Slavin wrote:
When "pragma integrity_check" detects an error, does "PRAGMA quick_check" do
too ?
Yes, both pragmas return same error.
Is your database file really about 65 Meg in size ? Just roughly.
Yes:
$ du -sh *
66M applianc
Hi,
On Wed, Dec 27, 2017 at 12:00 PM, Warren Young wrote:
> On Dec 27, 2017, at 7:49 AM, Nelson, Erik - 2
> wrote:
>>
>>> Also when you're forced to use a third party ticket system, fossil i
>>> missing one of its big advantages.
>>
>> I'm no Fossil expert, but it does seem to have a ticketing
On 27 Dec 2017, at 1:51pm, Fredrik Gustafsson wrote:
> - What are our demands for a ticket system, would fossil or gitlab (for
> example) suit us better?
Here’s something from experience.
You can have three types of ticket:
A) Internal tickets. These are raised by employees of your company w
On Dec 27, 2017, at 7:49 AM, Nelson, Erik - 2
wrote:
>
>> Also when you're forced to use a third party ticket system, fossil i missing
>> one of its big advantages.
>
> I'm no Fossil expert, but it does seem to have a ticketing system. Is there
> something in particular functionality missing
On Dec 27, 2017, at 3:23 AM, Rob Willett wrote:
>
> I know RCS is possibly older than the average reader on this mailing list,
> but it works very well for us and the workflow 'just works’.
Fossil “just works” for me, too.
I’m curious why Subversion never appealed to you, being that it’s RCS-d
While this is really entirely derailed I'll add...
If monotone wasn't dead 6 years now I'd be using that...but it doesn't
support unicode filenames very well; and they haven't wanted to do updates.
I was really resistant to migrating to Git; actually almost any other
alternaitve of them. Monotone
Fredrik Gustafsson Sent: Wednesday, December 27, 2017 8:52 AM
>Ask yourself if you want a system that is easy to use or easy to learn.
That feels like a false choice- why can't it be both easy to learn and easy to
use? That's a hallmark of good engineering.
>Also when you're forced to use a th
Hi,
I'm a former git developer and have been lurking on this maillist (since
I work with sqlite3) and followed fossil (since I'm interested in scm).
On Wed, Dec 27, 2017 at 10:23:57AM +, Rob Willett wrote:
> the commands were exceptionally confusing. It appeared to us that most of
> the docume
Dear all,
I've enjoyed reading about the Github vs Fossil discussion. There's been
some passionate and provocative statements :)
What its done for me is make me think again about how we manage our
source code control which is always good. We very recently moved from
our existing text based R
27 matches
Mail list logo
