On Sat, 13 Sep 2014 01:07:59 +0100
Simon Slavin wrote:
> > Implement a block-transaction store on the device
> > itself: no inodes, no directories, just writeable blocks managed in
> > transactions. Build your DBMS on that.
>
> That would be ... erm ... perhaps a new disk volume format. Wher
On Sat, Sep 13, 2014 at 11:01 AM, James K. Lowden
wrote:
> I used "database" because that was his word. Whether or not a
> filesystem is a database depends on the definition. I would say that
> the files are data, but the filesystem is not a DBMS, partly for
> reasons you mention. Do the files
On 13 Sep 2014 at 16:39, Richard Hipp wrote:
> I say that a filesystem is an eventually-consistent key/value database.
> The keys are the filenames and the values are all big BLOBs, specifically
> the file content. Filesystems also have a hierarchical keyspace, which is
> an extension from the
On 13 Sep 2014, at 6:16pm, Tim Streater wrote:
> On 13 Sep 2014 at 16:39, Richard Hipp wrote:
>
>> I say that a filesystem is an eventually-consistent key/value database.
>> The keys are the filenames and the values are all big BLOBs, specifically
>> the file content. Filesystems also have a
Simon Slavin wrote:
That's not what I meant. That's the file as a database. What I want is
the entire volume as a database.
That's exactly what I pointed you to before. The thesis is pretty enlightening
too.
http://www.fsl.cs.sunysb.edu/docs/kbdbfs-msthesis/
--
-- Howard Chu
CTO, Syma
On 13-9-2014 19:45, Simon Slavin wrote:
On 13 Sep 2014, at 6:16pm, Tim Streater wrote:
On 13 Sep 2014 at 16:39, Richard Hipp wrote:
I say that a filesystem is an eventually-consistent key/value database.
The keys are the filenames and the values are all big BLOBs, specifically
the file con
On 12/09/14 17:07, Simon Slavin wrote:
> Programmers don't expect file services to support transactions because file
> services have never supported transactions.
Ever hear of Windows and Transactional NTFS :-)
http://msdn.microsoft.com/en-us/magazine/cc163388.aspx
It turns out that adding tra
On Sat, Sep 13, 2014 at 9:39 AM, Richard Hipp wrote:
> I say that a filesystem is an eventually-consistent key/value database.
> The keys are the filenames and the values are all big BLOBs, specifically
> the file content. Filesystems also have a hierarchical keyspace, which is
> an extension fr
Scott Robison wrote:
On Sat, Sep 13, 2014 at 9:39 AM, Richard Hipp wrote:
I say that a filesystem is an eventually-consistent key/value database.
The keys are the filenames and the values are all big BLOBs, specifically
the file content. Filesystems also have a hierarchical keyspace, which is
On 13 Sep 2014, at 7:05pm, Roger Binns wrote:
> Ever hear of Windows and Transactional NTFS :-)
>
> http://msdn.microsoft.com/en-us/magazine/cc163388.aspx
>
> It turns out that adding transactions indiscriminately doesn't magically
> make everything better and lots of thought does need to be a
On 13 Sep 2014, at 7:01pm, Luuk wrote:
> On 13-9-2014 19:45, Simon Slavin wrote:
>
>> What I want is the entire volume as a database. It would be something like
>>
>> Key Example value
>> --- -
>> /robots.txt/path /
>>
On Fri, Sep 12, 2014 at 6:21 PM, Richard Hipp wrote:
> On Fri, Sep 12, 2014 at 8:07 PM, Simon Slavin
> wrote:
> >
> > one thing that annoys me about SQLite is that it needs to make a
> > journal file which isn't part of the database file. Why ? Why can't it
> > just write the journal to the
On Sat, Sep 13, 2014 at 2:46 PM, Simon Slavin wrote:
>
>
> > Before Unix came along it was quite common for files to be structured,
> > managed by the operating system and to be record based with file apis
> > working that way. Unix turned files (and similar) into unstructured
> bags of
> > byte
On 13 Sep 2014, at 8:43pm, Richard Hipp wrote:
> On Sat, Sep 13, 2014 at 2:46 PM, Simon Slavin wrote:
>
>> I would dispute that. [snip]
>
> Roger is correct.
>
> [description]
Thanks for the correction. Apologies to Roger for doubting him.
> You youngsters really have concept of the chao
On Sat, Sep 13, 2014 at 1:43 PM, Richard Hipp wrote:
> Decades ago, files came in all kinds of varieties and permutations.
> Details varied from one OS to the next. But it was common to have a
> distinction between text files and binary files (with different APIs for
> accessing each.) It was a
Scott Robison wrote:
On Sat, Sep 13, 2014 at 1:43 PM, Richard Hipp wrote:
Decades ago, files came in all kinds of varieties and permutations.
Details varied from one OS to the next. But it was common to have a
distinction between text files and binary files (with different APIs for
accessing
On 13 Sep 2014, at 9:16pm, Howard Chu wrote:
> Scott Robison wrote:
>
>> At the
>> very least (and I suspect more) Commodore 8-bit DOS (which was embedded
>> within a smart drive with its very own dedicated CPU & RAM) supported
>> (essentially) sequential byte stream files (no random seeking fo
Scott Robison wrote:
On Fri, Sep 12, 2014 at 6:21 PM, Richard Hipp wrote:
On Fri, Sep 12, 2014 at 8:07 PM, Simon Slavin
wrote:
one thing that annoys me about SQLite is that it needs to make a
journal file which isn't part of the database file. Why ? Why can't it
just write the journal
Hi all,
I have the following database where one of the entities in the database is
corrupted (dumping doesn't retrieve any data). Is there any way at all to
fix this database file or is it gone for good?
Harrys-Retina-MacBook-Pro:wetransfer-3bb6e0 Harry$ *ls*
ProjectDataBase.xcdatamodeld
Harrys
On Sat, Sep 13, 2014 at 2:24 PM, Howard Chu wrote:
> Scott Robison wrote:
>
>> A couple of academic thoughts.
>>
>
>> 1. If one wanted to embed the journal within the database, would it be
>> adequate to reserve a specific page as the "root" page of the journal,
>> then
>> allocate the remaining
Scott Robison wrote:
On Sat, Sep 13, 2014 at 2:24 PM, Howard Chu wrote:
Scott Robison wrote:
A couple of academic thoughts.
1. If one wanted to embed the journal within the database, would it be
adequate to reserve a specific page as the "root" page of the journal,
then
allocate the rema
On Sat, Sep 13, 2014 at 2:53 PM, Howard Chu wrote:
> Scott Robison wrote:
>
>> On Sat, Sep 13, 2014 at 2:24 PM, Howard Chu wrote:
>>
>> Scott Robison wrote:
>>>
>>> A couple of academic thoughts.
>>> 1. If one wanted to embed the journal within the database, would it be
adequat
Greetings!
I know that the IN clause contains a list of something. I.e.
IN ('2014-01-01', '2014-01-02', '2014-01-03', '2014-01-04', '2014-01-05')
So the question is, is there a shorter way for one to say something like,
IN ('2014-01-01', ..., '2014-01-05')
where the content of the IN would h
On 2014-09-13, 10:07 PM, jose isaias cabrera wrote:
I know that the IN clause contains a list of something. I.e.
IN ('2014-01-01', '2014-01-02', '2014-01-03', '2014-01-04', '2014-01-05')
So the question is, is there a shorter way for one to say something like,
IN ('2014-01-01', ..., '2014-01-0
24 matches
Mail list logo
