|
ObjStore::Internals is a Perl module with a few notes on the implementation. SYNOPSIS You dont have to understand anything about the technical implementation. Just know that: ObjectStore is outrageously powerful; sophisticated; and even over-engineered. The perl interface is optimized to be fun and easy. Since ObjectStore is also blindingly fast, you can happily leave relational databases to collect dust on the bookshelf where they belong. So basically, you dont have to understand anything to a greater depth. Its not necessary. Youve arrived. You will be successful. However, more detail follows. If you like to turn things inside-out, read on! Perl & C++ APIs: Whats The Difference? Most stuff should be roughly the same. The few exceptions have generally arisen because there was a perl way to make the interface more programmer friendly. Transactions are perlified. Some static methods sit directly under ObjStore:: instead of under their own classes. (Easier to import.) Databases are always blessed according to your pleasure. lookup, open, is_open, and lock_timeout are augmented with multi-color, pop-tart style interfaces. Why not just store perl data with the usual perl structures? CHANGE CONTROL As perl evolves, new data layouts are introduced. These changes must not cause database compatibility problems. BINARY COMPATIBILITY Perl doesnt have to worry about binary compatibility between platforms. Databases do. In addition, databases impose a number of restrictions on persistent data layout that would be onerous and sub-optimal if adopted by perl. MEMORY USAGE Perl often trades memory for speed. This is the wrong trade for a database. Memory usage is much more of a concern when data sets can be as large or larger than ten million megabytes. A few percent difference in compactness can be quite noticable..
|
Windows Software
Albina Merfyn - I find this to be really easy to use. I can...
