Re: Call for testing experimental patch

["Chris Travers" <..hidden..>]

I would like to see as many aspects of the other tables moved into
transaction_ledger as possible.  So transaction_ledger is probably an
accurate if cumbersome name.

I will concede that "transactions" and "transaction_ledger" are both
names that describe the table well enough.  The former is a little
shorter, but the other tables are all singluar and "transaction" is a
reserved word.  So the name was chosen carefully, but "transactions"
might have been a viable and adequate name as well.

Best Wishes,
Chris Travers

On 9/19/06, David Tangye <..hidden..> wrote:
> On Tue, 2006-09-19 at 11:34 -0700, Tony Fraser wrote:
> > Would it be better to call this table simply 'transactions'?
> > 'transaction_ledger' works for me if it's too late to change it now.
> :-). Its a comment I have made before: its really important to decide
> what the table represents - what its purpose is, and then its important
> to give it a name that reflects this as concisely and unambiguously as
> possible.
> So the question is: what exactly is the purpose of the table, now and in
> the future? Agree that and the best name should become clear.
>
> One of the best indicators of a stuffed, buggy system is simply to look
> at table, column and constraint names and see that they don't reflect
> clearly exactly what the data in there actually is.
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Ledger-smb-devel mailing list
> ..hidden..
> https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel