the URL still is a problem: it needs to specify the database type (JDBC subprotocol)
dbfs://user:[EMAIL PROTECTED]:host:dbname/ OR dbfs:subprotocol://user:[EMAIL PROTECTED]:dbname/ if we plan on making use of intermediats like hibernate, we may or may not put that in the url too or leave that to internal configuration dbfs:hyb3:DBCP:mysql://user:[EMAIL PROTECTED]:dbname/ dbfs:JDBC:mysql://user:[EMAIL PROTECTED]:dbname/ sugestions? Wouter On Mon, 28 Mar 2005 15:03:39 +0200, Wouter De Borger <[EMAIL PROTECTED]> wrote: > No, it's good, > > so, i've made up my mind for a 0.1 version, > > structure: > -inodes (with links) > -metadata ������how long sould the blob feeld be?????? (we could > split them up, but that's kind of out of scope I think) > -chunks (they have numbers to reconstruct them in the right order) > -chunksize as an attribute (metadata for inode 0), > -max filesize as an attribute > implentation > -plain jdbc (I'll add hybernate or whatever later on, I'd like to > hold off all the external configuration until we have something to > work on) > > so, when I have some time, I'll get it done > > Wouter > > > On Mon, 28 Mar 2005 12:25:24 +0200, Mario Ivankovits <[EMAIL PROTECTED]> > wrote: > > Wouter De Borger wrote: > > >but I presume this is the one file one blob version? > > > > > Yes. One file one Blob. Now I have seen your Content has a number - what > > was the indention of it? > > Every entry (file/directory/link) do have only one inode which is unique > > for the whole filesystem. > > E.g. this makes it easy to rename/move a whole tree. > > >or am I wrong (the parts can be clustered with the link field, but > > >that would require a lot of duplicate inode data?) > > > > > The "link" field was meant to allow inserting the same inode at another > > place in the structure > > > > e.g. > > > > /root/dir1/file1.txt > > /root/dir2/file2.txt > > /root/dir2/file3.txt -> /root/dir1/file1.txt > > > > which means file3.txt is the same as file1.txt e.g. its link_inode > > points to the same inode as file1.txt. > > > > This is called "hard link" and only possible within the same filesystem > > - in other word its topmost parent_inode has to be the same as the link > > destination. > > > > But hey. For sure we wont need this for version 1.0 - Maybe I carried > > too far ;-) > > > > --- > > Mario > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > > Gmail rules > --------------------------------------------------------------------- > Wouter De Borger > --------------------------------------------------------------------- > if life was a joke of eternity, what would you do? > All I want is a kind word, a warm bed and unlimited power. > --------------------------------------------------------------------- > www.nosoftwarepatents.com > -- Gmail rules --------------------------------------------------------------------- Wouter De Borger --------------------------------------------------------------------- if life was a joke of eternity, what would you do? All I want is a kind word, a warm bed and unlimited power. --------------------------------------------------------------------- www.nosoftwarepatents.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
