Slashdot Mirror

← Back to Stories (view on slashdot.org)

SQL Over FreeNet

Posted by CmdrTaco on from the allright-thats-pretty-impressive dept.

Nym writes: "It seems that another component, SQL has been added to the many layers of Freenet. Check out FreeSQL Project, and start porting your SQL apps today." The possible implications of this sort of utility are amazing.

3 of 95 comments (clear)

  1. is this really newsworthy? by Sanity · · Score: 5
    While it is good to see anyone creating anything over Freenet, I have some issues with this:
    • Is this even newsworthy? There is no code, not even a homepage, nothing to suggest this isn't vapourware (of which there is no shortage on Sourceforge)
    • Freenet isn't very well suited to this task because it forgets unpopular information, which is just what you don't want a database to do
    Note that the lack of permenant data is not a flaw in Freenet, in this regard Freenet is more like a radio station than a library, or indeed, a database. Before anyone says "but why not just add permenant data to freenet" know that someone suggests this on the freenet mailing lists about once every two days - it isn't possible while staying true to Freenet's other goals.

    --

  2. Truly, you have a dizzying intellect. by Salamander · · Score: 5

    I love it. Forget all that ACID crap, especially the D part, let's put a database interface on top of a storage system that is designed to drop data practically at random. Brilliant. I can't imagine why nobody thought of this before.

    --
    Slashdot - News for Herds. Stuff that Splatters.
  3. How do they handle all that extra loading exerted? by jsse · · Score: 5

    Those who tried out FreeNet know that it's slow, and it's expectable.

    However, SQL is kind of very load-demanding accessing method. Anyone who could put an excess amount of loading to the network by running an open end SQL with sorting(just an example):

    SELECT * FROM FREENET.BIG_TABLE WHERE 1=1 OR 2=2 ORDER BY 1

    A similar carelessly written statement of above crashed an enterprise database once because excessive TEMP spaced was requested for open end sorting.

    How do they deal with the stability/performance in favour of accessibility?