• olygofren (unregistered)

    Pretty good stuff though the obfuscation was a bit lame ;)

    An intriguing mix of prank and some really interesting and useful code I learned a lot from, 10x.

  • Jay (unregistered)

    Bah, this system has the obvious flaw that it is totally vulnerable to hardware failures.

    The real wave of the future is a recent invention called "punch cards". They are totally impervious to magnetic anomolies and head crashes. They have even been proven to be capable of withstanding an EMP attack. They are inherently both machine-readable and human-readable. Indeed, the data is still accessible even if your sever is completely down! What other database can guarantee that?

  • IsItEverFastEnough (unregistered) in reply to Ike

    The database won't work with my system. Oh, wait... SHIT! My WD drive model number ends in 'S'!!!

    Hysterical.

  • swschrad (unregistered) in reply to ircmaxell

    red flag: "There are no known bugs."

    even if it was programmed by monkeys on crack, there would be known bugs.

    if there is one operator and one operand in a program, there must be a bug. that is a given.

  • Stinky (unregistered)

    If you want state of the art, try the FSDB. The "File system Data Base" uses the findfirst() and findnext() file system directory functions to index your objects. Using symblic links, it even acts relationally. With the FSDB you simply create directories instead of tables. Then you persist your objects to files in these directories.

  • not very decent (unregistered) in reply to Costanza
    Costanza:
    you sure it's not Not Too F'ing Smart?
    Quite.
  • hoodaticus (unregistered)

    Now if we can just replace the Wheel, we'll be ready to move into the 22nd century.

  • (cs) in reply to hoodaticus
    hoodaticus:
    Now if we can just replace the Wheel, we'll be ready to move into the 22nd century.

    With jet packs!

  • (cs) in reply to hoodaticus
    hoodaticus:
    Now if we can just replace the Wheel, we'll be ready to move into the 22nd century.

    With jet packs!

  • Paperless (unregistered) in reply to Jay
    Jay:
    Bah, this system has the obvious flaw that it is totally vulnerable to hardware failures.

    The real wave of the future is a recent invention called "punch cards". They are totally impervious to magnetic anomolies and head crashes. They have even been proven to be capable of withstanding an EMP attack. They are inherently both machine-readable and human-readable. Indeed, the data is still accessible even if your sever is completely down! What other database can guarantee that?

    My refrigerator magnet database has been up and running since 1981. I'm thinking of upgrading with a web cam, so I can access it from work.

  • Paperless (unregistered)

    Funny. The odd bug is - APDB needs an external database to manage the keys, otherwise how do you find where you put which keyed data?

  • RRR (unregistered)

    Wow! Cool! Wait... What?!...

  • Yanman (unregistered)

    But can it run Crysis?

  • WaltDismal (unregistered)

    My client SCO had me contact you since they own the rights to one-click direct data addressing, which they tell me they bought from Ada Lovelace. You owe us eleventy bazillion dollars for infringement. Also, I have notified the RIAA that your cat downloads mice illegally. Don't mess with us, we know what we're doing.

    Sincerely,

    A. G. Douchebag

  • Sam (unregistered)

    Hey kinda new to this but doesn't this limit you to using only certain drive types. Also what about the merger into solid state drives. And would you ever need to defrag? Juwst some thoughts. But I surely like the concept.

  • damnum (unregistered)

    Pretty similar to something I was doing in the mid 80's, and generally pissing over what SQL could provide.

  • Norman Rorqual (unregistered)

    This is pretty great, but...I can't imagine what that EXE file he linked at the end would actually DO. Can anybody explain for those of us who may be a bit rusty on our hex-editor hacking?

  • JasonD (unregistered)

    So... How well does this play with "Spread Writes", which is done by the HD, not the OS?

    How well does this work if something decides to defrag, and relocate data to new cells, to keep it contiguous?

    How well does this work, per volume of data? Any time-demos?

    Times using simple 2D arrays (rows/columns), 3D arrays (row/column/page), xD arrays... Non-format data (raw) and (non-fixed length)... 1000 entries on 1000 tables, and 10000000 entries on 100000000 tables... and table/cell/data locking...

    Failed-erase, Failed-writes, sorting, condensing for duplication/backup for later expansion... (Has to repopulate the same cells, which may now be other data. Thus destructive restoration, thus must inject and re-create the whole DB every time... That is a LOT of time just to restore, and what to do with new data, not restored.)

  • Oscar Carserud (unregistered)

    Hmm. Sounds like the grana software db to vic64. Exept that was flopy disc times. The logic is the same. The sweet 80 ies. As the 90 arrived, I remember the yoy of relational databases as they where a new consept.

  • Luciano Seibel (unregistered)

    Hello... I'm late to the discussion but I'll try. Is there the source for download yet ? Tks.

Leave a comment on “Announcing APDB: The World's Fastest Database”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article