Captured some thoughts, some experiments on how to tie statement entry to ledger entry. It's not at all clear we want to go down this (or any other) path at the moment. This checkin will probably go nowhere, as I'm going to see if we can make do with the current implementation.

git-svn-id: file:///svn-source/pmgr/branches/statement_ledger_entry_tie_20090802@468 97e9348a-65ac-dc4b-aefc-98561f571b83

db/schema.sql

@@ -1000,9 +1000,9 @@ CREATE TABLE `pmgr_transactions` (
 ) ENGINE=MyISAM DEFAULT CHARSET=utf8;
 
 
--- -- ----------------------------------------------------------------------
--- -- ----------------------------------------------------------------------
--- -- TABLE pmgr_ledger_entries
+-- ----------------------------------------------------------------------
+-- ----------------------------------------------------------------------
+-- TABLE pmgr_ledger_entries
 
 DROP TABLE IF EXISTS `pmgr_ledger_entries`;
 CREATE TABLE `pmgr_ledger_entries` (
@@ -1028,9 +1028,9 @@ CREATE TABLE `pmgr_ledger_entries` (
 ) ENGINE=MyISAM DEFAULT CHARSET=utf8;
 
 
--- -- ----------------------------------------------------------------------
--- -- ----------------------------------------------------------------------
--- -- TABLE pmgr_double_entries
+-- ----------------------------------------------------------------------
+-- ----------------------------------------------------------------------
+-- TABLE pmgr_double_entries
 
 DROP TABLE IF EXISTS `pmgr_double_entries`;
 CREATE TABLE `pmgr_double_entries` (
@@ -1053,9 +1053,9 @@ CREATE TABLE `pmgr_double_entries` (
 ) ENGINE=MyISAM DEFAULT CHARSET=utf8;
 
 
--- -- ----------------------------------------------------------------------
--- -- ----------------------------------------------------------------------
--- -- TABLE pmgr_statement_entries
+-- ----------------------------------------------------------------------
+-- ----------------------------------------------------------------------
+-- TABLE pmgr_statement_entries
 
 DROP TABLE IF EXISTS `pmgr_statement_entries`;
 CREATE TABLE `pmgr_statement_entries` (
@@ -1090,12 +1090,9 @@ CREATE TABLE `pmgr_statement_entries` (
 
   `amount`               FLOAT(12,2) NOT NULL,
 
-  -- The account of the entry
-  -- REVISIT <AP>: 20090720
-  --  We don't want to confuse statement entries with ledger entries,
-  --  yet we're including account here.  It doesn't feel right, but at
-  --  the same time, it will allow us to show _what_ was charged for
-  --  in the statement.  Keeping it for now...
+  -- Account ID is used only for those statement entries that have
+  -- a guaranteed single ledger entry, and thus single account.
+  -- Right now, this is only used for charges.
   `account_id`           INT(10) UNSIGNED DEFAULT NULL,
 
   -- Allow the payment to reconcile against the charge
@@ -1107,6 +1104,27 @@ CREATE TABLE `pmgr_statement_entries` (
 ) ENGINE=MyISAM DEFAULT CHARSET=utf8;
 
 
+-- ----------------------------------------------------------------------
+-- ----------------------------------------------------------------------
+-- TABLE pmgr_statement_entries_ledger_entries
+-- TABLE pmgr_statement_fractions
+
+DROP TABLE IF EXISTS `pmgr_statement_fractions`;
+CREATE TABLE `pmgr_statement_fractions` (
+  `id`                   INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
+
+  -- The two entries that make up a "double entry"
+  `statement_entry_id`   INT(10) UNSIGNED NOT NULL,
+  `ledger_entry_id`      INT(10) UNSIGNED NOT NULL,
+
+  `amount`               FLOAT(12,2) NOT NULL,
+
+  `comment`              VARCHAR(255) DEFAULT NULL,
+
+  PRIMARY KEY (`id`)
+) ENGINE=MyISAM DEFAULT CHARSET=utf8;
+
+
 -- ----------------------------------------------------------------------
 -- ----------------------------------------------------------------------
 -- TABLE pmgr_tender_types