Hi John;
I have added you to the contrutors file. Most of your changes were
accepted. A few were rejected because parts of the manual were out of
date and were removed.
Anyway, thanks for your contributions.
Best Wishes,
Chris Travers
On 10/30/06, John Hasler <[EMAIL PROTECTED]> wrote:
> Here
SL 2.x to LSMB 1.1 should be an easy migration. However, we are
diverging rapidly as you point out. In fact, our 1.2 changelog is
about 50 lines (including a few blank lines and section headers).
LSMB 1.2 will be a harder migration for anybody. 1.3 may be too.
After that, we expect things to sm
I am currently using SQL Ledger internally and for multiple hosted clients. I would love to migrate to LedgerSMB but wonder how you plan to handle this process after multiple development cycles for both products. Right now the code is pretty similar but what about in 6 months when there has been
Hi Ed;
On 11/7/06, Ed W <[EMAIL PROTECTED]> wrote:
> Hi
>
> I have done a few projects where we stuck a lot of code on the DB server
> and whilst it's nice in theory, it did lead to a DB performance
> bottleneck, and it is a bit limiting when later on you suddenly wish
> that you could support oth
On 11/6/06, Jeff Gerritsen <[EMAIL PROTECTED]> wrote:
> On Mon November 6 2006 12:45, Chris Travers wrote:
> > ...
> > We are moving in that general direction. However, there are
> > legitimate questions about how far to take this. Certainly we intend
> > to get all the logic out of the UI code a
Ed,
> I have done a few projects where we stuck a lot of code on the DB server
> and whilst it's nice in theory, it did lead to a DB performance
> bottleneck, and it is a bit limiting when later on you suddenly wish
> that you could support other databases after all (eg replication is
> stronger i
Hi,
Hope I'm not intruding too much here, but I've been keeping an eye on
the project, and since I'm nearing the end of a big custom
Postgresql/PHP app, have some thoughts here...
Chris Travers wrote:
> On 11/6/06, David Ratte <[EMAIL PROTECTED]> wrote:
>
>> Currently there is 'logic' in both
Hi
I have done a few projects where we stuck a lot of code on the DB server
and whilst it's nice in theory, it did lead to a DB performance
bottleneck, and it is a bit limiting when later on you suddenly wish
that you could support other databases after all (eg replication is
stronger in MySql
On Mon November 6 2006 12:45, Chris Travers wrote:
> ...
> We are moving in that general direction. However, there are
> legitimate questions about how far to take this. Certainly we intend
> to get all the logic out of the UI code and move to a templating
> system. Certainly we intend to put mo
