On Mon, Oct 3, 2011 at 2:50 PM, Erik Huelsmann wrote:
> Hi Chris,
>
>
>
>> Also logically it changes things to the following under the above proposal:
>> 1) Every AR and every AP transaction is also a journal entry
>> 2) Every payment and every receipt is now a full transaction and journal
>>
Hi Chris,
On Mon, Oct 3, 2011 at 7:25 PM, Chris Travers wrote:
> Hi all;
>
> I would like to go forward with my database refactoring proposal for
> 1.4. This is an outgrowth of two things, Josh Drake's feature request
> that we merge the AR and AP tables and my work on restoring
> referential in
On Mon, Oct 3, 2011 at 11:22 AM, John Locke wrote:
> Hi,
>
> Initial thoughts: Sounds like a huge improvement, and it mostly makes
> sense to me.
>
> The one area I'm not clear on is inventory management, and whether oe
> and order_items should get rolled into the same tables as ar/ap/invoice.
>
>
I keep thinking about this, and again, I may be way off base, but I'm
thinking we're missing a historical component here, particularly in orders.
Again, I look to how Drupal addresses this, and for content, this is
done by splitting a node into two tables: node and node_revision. If you
add fields
Hi,
Initial thoughts: Sounds like a huge improvement, and it mostly makes
sense to me.
The one area I'm not clear on is inventory management, and whether oe
and order_items should get rolled into the same tables as ar/ap/invoice.
I may be totally off-base here, but I'm thinking that invoices are
Hi all;
I would like to go forward with my database refactoring proposal for
1.4. This is an outgrowth of two things, Josh Drake's feature request
that we merge the AR and AP tables and my work on restoring
referential integrity to the database. The current problem is that
acc_trans.trans_id ref
