headers
Chris Travers | 6 Aug 2008 17:58
Picon

Proposed changes in trunk: adding mappings to entity_credit_account for addresses, etc

Currenty, in trunk, all addresses, contact info, etc are mapped back
to a company or person entity.  We do not have mappings per
customer/vendor account.

I have had at least one request for contract (entity_credit_account)
to address mappings in the following way:
1)  Every entity_credit_account can only have one billing address
2)  Any number of contacts per entity_credit_account record
3)  One bank account listed per entity_credit_account (for automated payments)
4)  Notes that can be attached to either the entity or contract

I suspect that there could be a more general need for billing and
contact to map to actual customer accounts than is just with this
company, so I am asking whether everyone else feels like the above
rules are generally applicable.  Any thoughts?

Best Wishes,
Chris Travers

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Permalink | Reply | 6 comments |
headers
Chris Travers | 8 Aug 2008 19:12
Picon

Re: Proposed changes in trunk: adding mappings to entity_credit_account for addresses, etc

On Wed, Aug 6, 2008 at 8:58 AM, Chris Travers
<chris.travers@...> wrote:
> Currenty, in trunk, all addresses, contact info, etc are mapped back
> to a company or person entity.  We do not have mappings per
> customer/vendor account.
>
> I have had at least one request for contract (entity_credit_account)
> to address mappings in the following way:
> 1)  Every entity_credit_account can only have one billing address
> 2)  Any number of contacts per entity_credit_account record
> 3)  One bank account listed per entity_credit_account (for automated payments)
> 4)  Notes that can be attached to either the entity or contract

Currently the technical proposals include:

1)  New mapping tables eca_to_contact and eca_to_location which are
similar in strcture to company_to_contact and company_to_location.
These, along with person_to_contact and person_to_location should
probably be moved into an inherited tree of tables for better
management similar to what we do with notes.  The old tables would
continue to be used for contact info which is not mapped to a
contract.

2)  New stored procedure API's which retrieve contacts and locations
by credit_id rather than company_id.

3)  A partial index on eca_to_location as follows:
CREATE UNIQUE INDEX eca_to_location_billing_u ON
eca_to_location(credit_id) WHERE location_class = 1;
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeff Kowalczyk | 10 Aug 2008 16:40
Picon
Favicon

Re: Proposed changes in trunk: adding mappings to entity_credit_account for addresses, etc

Chris Travers wrote:
> Currenty, in trunk, all addresses, contact info, etc are mapped back
> to a company or person entity.  We do not have mappings per
> customer/vendor account.
> 
> I have had at least one request for contract (entity_credit_account)
> to address mappings in the following way:
> 1)  Every entity_credit_account can only have one billing address
> 2)  Any number of contacts per entity_credit_account record
> 3)  One bank account listed per entity_credit_account (for automated payments)
> 4)  Notes that can be attached to either the entity or contract
> 
> I suspect that there could be a more general need for billing and
> contact to map to actual customer accounts than is just with this
> company, so I am asking whether everyone else feels like the above
> rules are generally applicable.  Any thoughts?

Are the instances of 'contract' typos for 'contact'?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Permalink | Reply | 1 comment |
headers
Chris Travers | 11 Aug 2008 18:04
Picon

Re: Proposed changes in trunk: adding mappings to entity_credit_account for addresses, etc

In this case, "contract" is a vendor account, but it could be a
customer account as well.
Best Wishes,
Chris Travers

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Permalink | Reply | 0 comments |
headers
Jeff Kowalczyk | 11 Aug 2008 22:34
Picon
Favicon

Distributed LedgerSMB Development With DVCS - Git

=================================================
Distributed LedgerSMB Development With DVCS - Git
=================================================
2008-08-11
By Jeff Kowalczyk (jfkw)

I've been working on my local LedgerSMB deployment customization
using the distributed version control system, git. I'm relatively
new to git, but it's really helping me in the following areas:

* Fixing bugs in branches/1.2

* Making necessary customizations that are unsuitable for
  upstream

* Layering multiple customization branches on each other to get
  the configuration required by a particular customer deployment

* Putting templates and graphics under version control

* Putting the plaintext backup of the company database under
  version control. At any time I can and do make snapshots, then
  examine the diff to see how each LedgerSMB operation affects
  the database tables.

LedgerSMB Development and DVCS
==============================

The LedgerSMB projet is organized around a team of core-devs,
with exclusive commit priviledges to the centralized subversion
(Continue reading)

Permalink | Reply | 6 comments |
headers
Chris Travers | 12 Aug 2008 18:11
Picon

1.2.14 released

Hi all;

LedgerSMB 1.2.14 has been released.  This is a maintenance release
which includes bugfixes only.  The complete changelog is:

* Build.PL now requires Test::Trap (Chris T, 1872529)
* Fixed double escaping of tex under some circumstances (Seneca)
* Added fix for bad summary information in AR/AP transactions (1800065,
1800069, Chris T)
* Fixed posting issue behind AR/AP transaction report anomilies (Chris T)
* Fixed taxes added twice when viewing existing transaction (Chris T)
* Fixed erroneous discount lines in POS invoice (Chris T)

Thanks,
The LedgerSMB Team

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Permalink | Reply | 0 comments |
headers
Chris Travers | 13 Aug 2008 03:06
Picon

Re: Distributed LedgerSMB Development With DVCS - Git

Before I add a couple of tiny nit-picks to Jeff's post I want to say
that I think that this could be a very good thing for the project.
This provides a way for people to create changes in a well-reviewed
way, provide more open development of patches, etc.

> * Putting the plaintext backup of the company database under
>  version control. At any time I can and do make snapshots, then
>  examine the diff to see how each LedgerSMB operation affects
>  the database tables.

BTW, a better idea would be to turn on statement logging and revision
control your logs :-)  database backups can be problematic for
revision control for a number of reasons including the dump order of
the rows.

If anyone needs to know how to do this, let me know :-)

>
> LedgerSMB Development and DVCS
> ==============================
>
> The LedgerSMB projet is organized around a team of core-devs,
> with exclusive commit priviledges to the centralized subversion
> repository hosted on Sourceforge.

Actually, we are organized around a core committee which is not
exactly equal to the committing members (though they currently are
equal in number).  One of the core committee members does not have
commit priv's and one non-core committee member does have commit
priv's.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeff Kowalczyk | 13 Aug 2008 14:02
Picon
Favicon

pg_dump, statement logging and revision control of a company database

> > Putting the plaintext backup of the company database under version
> > control. At any time I can and do make snapshots, then examine the
> > diff to see how each LedgerSMB operation affects the database tables.
>
> BTW, a better idea would be to turn on statement logging and revision
> control your logs :-)  database backups can be problematic for revision
> control for a number of reasons including the dump order of the rows.
>
> If anyone needs to know how to do this, let me know :-)

I'll bite. Let's document each method here for the benefit of the list
readers. I think they may be complementary.

I have been using pg_dump, via two convenience scripts (per company)

backup.sh:
pg_dump --format=p -c -U postgres mycompany --file=mycompany.sql

restoredb.sh:
psql -U postgres -d ledgercdog -f ledgercdog.sql

with mycompany.sql under revision control. This allows one to:

- get a birds-eye view of the whole changed row(s), including defaults,
  empty strings and NULLs.

- easily go back to any previous snapshot

The limitation Chris mentioned, that pg_dump tables are not sorted, is
exactly right. Usually pg_dump generates the same or similar sort
(Continue reading)

Permalink | Reply | 501 comments |
headers
Jeff Kowalczyk | 13 Aug 2008 14:17
Picon
Favicon

Re: pg_dump, statement logging and revision control of a company database

Typo correction:

backup.sh:
pg_dump --format=p -c -U postgres mycompany --file=mycompany.sql

restoredb.sh:
psql -U postgres -d mycompany -f mycompany.sql

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Permalink | Reply | 501 comments |
headers
John Locke | 14 Aug 2008 19:20
Favicon

Re: Distributed LedgerSMB Development With DVCS - Git

Hi,

Great writeup/tutorial, Jeff. Looks like there's a lot of people 
starting to switch to git. We've just done this internally in the past 
couple of months. One of the reasons was so that we could start 
incorporating UI changes to LSMB, pulling in the Dojo Toolkit to provide 
a lot better widget support on the browser (and more).

Business needs have kept me from even starting this work--but I hope to 
be digging in soon. At least we've figured out the code management 
challenges...

Meanwhile, we have a public git server set up that is tracking the LSMB 
Subversion repository. Anybody can browse it at 
http://git.freelock.com/?p=ledgersmb.git;a=summary . If you want to 
clone or pull from it, use git://git.freelock.com/git/ledgersmb.git . It 
gets automatically updated from svn every 6 hours. Right now this 
command will get you started, downloading a local copy of the entire 
LSMB history, saving you about a day of downloading:

git clone git://git.freelock.com/git/ledgersmb.git

Once we get started, you'll see some freelock branches in there... 
Anything we post to this git repository can be used under the same 
license terms as the LedgerSMB project itself.

Cheers,

--

-- 
John Locke
(Continue reading)

Permalink | Reply | 0 comments |

Gmane