lore 0.4.2 → 0.4.3

data/History.txt

@@ -0,0 +1,10 @@
+=== 0.4.2 / 2008-11-10
+
+* Major performance increase due to
+  * Optimized queries
+  * Mmap caching
+  * Minor refactoring - major effects
+  * Overhead of Lore is quite the same as Rails::ActiveRecord's
+* Further unit tests 
+* Extended prepared statements
+

data/Manifest.txt

@@ -0,0 +1,7 @@
+History.txt
+Manifest.txt
+README.txt
+Rakefile
+bin/lore
+lib/lore.rb
+test/test_lore.rb

data/Rakefile

@@ -0,0 +1,12 @@
+# -*- ruby -*-
+
+require 'rubygems'
+require 'hoe'
+require './lib/lore.rb'
+
+Hoe.new('lore', Lore::VERSION) do |p|
+  p.rubyforge_name = 'lore' # if different than lowercase project name
+  p.developer('Tobias Fuchs', 'fuchs@wortundform.de')
+end
+
+# vim: syntax=Ruby

data/bin/setup_db.rb

@@ -0,0 +1,9 @@
+
+require 'lore'
+
+module Lore
+
+  Context.enter(ARGV[1])
+  Connection.perform(setup_query)
+
+end

data/{README → lib/lore/README.txt}

@@ -3,31 +3,41 @@ Q: Are there adapters for other DBMS than PostgreSQL?
 A: PostgreSQL is - to me and everyone using Lore i know of - 
    the best (free) choice for sophisticated database-driven 
    apps, so frankly said: Implementing adapters is not on my
-   top priority list. Adapters also come with some cost in 
-   performance, by introducing an additional level of 
-   abstraction. 
+   top priority list. 
    So far, Lore supports PostgreSQL (7.4 to 8.3 tested). 
    Adapters are planned for oracle mysql and sqlite though. 
    Lore is SQL 92 compatible and not using any exotic 
    Postgres features, so it *might* work fine on e.g. mysql 
-   and sqlite with just minor modifications. It is caring 
-   about cascading dependencies etc, so you don't even need 
-   foreign keys or table inheritance. 
+   and sqlite with just minor modifications. Lore is caring 
+   about cascading dependencies etc itself, so you don't even 
+   need foreign keys or table inheritance. 
    You will have to change the code establishing DB 
    connections (see connection.rb), but as those are 
    abstracted, just a couple of lines of code in connection.rb
    had to be changed. 
 
 Q: How do i establish a DB connection at all? 
-A: In /lore.rb, edit the Hash instance @logins. Lore is caring 
-   about connections itself. 
-   You have to enter a so-called context (database, that is), 
-   though: 
+A: First provide login data for a database (aka Context): 
 
-     Lore::Context.enter :my_dbname
+     Lore.add_login_data('dbname' => ['user', 'pass'])
+     Lore.add_login_data('other_dbname' => ['user', 'pass'])
+
+   Now, activate a context. You can stack them, too: 
+
+     Lore::Context.enter :dbname
+     # Operate in database dbname
+     Lore::Context.enter :other_dbname
+     # Operate in database other_dbname
+     Lore::Context.leave
+     # Operate in database dbname
+     Lore::Context.enter :other_dbname
 
 Q: What about connection pooling? 
-A: Use PGPool for that, it's way better than any 
+A: Lore re-uses connections per-process, that is: There is 
+   one connection for every context you entered in every 
+   process Lore is running in. 
+   In case you need connections shared over multiple 
+   processes, use PGPool for that, it's way better than any 
    implementation of connection pooling in ruby. 
    Install PGPool and tell lore to connect to PGPool's port 
    instead of PostgreSQL's one. 
@@ -38,15 +48,16 @@ A: Use PGPool for that, it's way better than any
    That's it! 
 
 Q: Which solution do you recommend for query result caching? 
-A: There are many possibilities: Tempfiles, MMap and Memcached
+A: There are many possibilities: Tempfiles, Mmap and Memcached
    are the most widespread solutions known to me. 
    Many will agree that MMap is the best solution in matters 
    of performance on a single server, and memcached as soon as
    more than one server is involved in your application. 
+   To enable caching for all models: 
 
-Q: There are failing unit tests!!
-A: I know. Those document missing features i'm implementing 
-   at the very moment :)  Be sure to update once in a while! 
+     Lore::Model.use_entity_cache Lore::Cache::Mmap_Entity_Cache
+   or
+     Lore::Model.use_entity_cache Lore::Cache::Memcached_Entity_Cache
 
 Q: After creating a model via Model_Factory: How do i change 
    it? 
@@ -54,8 +65,7 @@ A: At the moment, this is not implemented, but tracked as
    'missing feature'. This will be possible in version 1.0 at 
    the latest. 
 
-Q: There's so much documentation missing, the API isn't really 
-   helpful. Where can i get more info and examples? 
+Q: Where to look for documentation and examples? 
 A: Have a look at the wiki. I'm updating it quite often, and 
    new features are explained in the wiki first: 
    http://infranode.com/wiki/

data/{cache → lib/lore/cache}/mmap_entity_cache.rb

@@ -1,7 +1,11 @@
 
 require 'lore'
 require 'lore/cache/abstract_entity_cache'
-require 'mmap'
+begin
+  require 'mmap'
+rescue LoadError
+  Lore.log { 'Mmap for Ruby could not be found. You won\'t be able to use Mmap_Entity_Cache. ' }
+end
 
 module Lore
 module Cache

data/{connection.rb → lib/lore/connection.rb}

@@ -3,7 +3,7 @@ $:.push('/opt/local/lib/ruby/1.8/postgres')
 
 require('postgres')
 require('logger')
-require('lore/lore')
+require('lore')
 require('lore/result')
 
 module Lore

data/{validation → lib/lore/validation}/reason.rb

@@ -1,6 +1,5 @@
 
 require('lore/validation/message')
-require('htmlentities')
 
 module Lore
 module Validation
@@ -12,8 +11,7 @@ module Validation
     attr_reader :options
 
     def message()
-      # polish message for html output: 
-      return @message.map { |m| HTMLEntities.new.decode(m) }
+      @message
     end 
     
     def initialize(message, options) # {{{

data/{lore.rb → lib/lore.rb}

@@ -2,6 +2,8 @@
 require('logger')
 
 module Lore
+  
+  VERSION='0.4.3'
 
   @logfile = '/var/log/lore/query.log'
   def self.logfile

data/lore.gemspec

@@ -14,25 +14,27 @@ spec = Gem::Specification.new { |s|
     and result caching using memory mapping (MMap). 
     Lore is currently using PostgreSQL as database backend. 
   EOF
-  s.version = '0.4.2'
+  s.version = '0.4.3'
   s.author = 'Tobias Fuchs'
   s.email = 'fuchs@atomnode.net'
   s.date = Time.now
   s.files = '*.rb'
-  s.add_dependency('mmap', '>= 0.1')
   s.add_dependency('postgres', '>= 0.1')
   s.files = FileList['*', 
-                        'behaviours/*', 
-                        'test/*', 
-                        'cache/*', 
-                        'validation/*', 
-                        'gui/*', 
-                        'gui/templates/*', 
-                        'exception/*'].to_a
+                     'lib/*', 
+                     'lib/lore/*', 
+                     'lib/lore/behaviours/*', 
+                     'lib/lore/cache/*', 
+                     'lib/lore/validation/*', 
+                     'lib/lore/gui/*', 
+                     'lib/lore/gui/templates/*', 
+                     'lib/lore/exception/*', 
+                     'bin/*', 
+                     'test/*'].to_a
 
   s.has_rdoc = true
   s.rdoc_options << '--title' << 'Lore ORM' <<
-                       '--main' << 'README' <<
+                       '--main' << 'README.txt' <<
                        '--line-numbers'
 
   s.homepage = 'http://lore.rubyforge.org'

data/test/custom_models.rb

@@ -0,0 +1,18 @@
+
+require('lore/model') 
+
+module Some
+module App
+
+  class New_Model < Lore::Model 
+    table :new_model, :public
+    primary_key :model_id, :model_id_seq
+    has_attribute :name, Lore::Type.integer
+    has_attribute :created, Lore::Type.timestamp
+    has_attribute :model_id, Lore::Type.integer
+
+
+  end
+end
+end
+