I released 1.3.43rc3. Please test it. It seems to work for me on some
limited test cases (on an existing db) but I would really like more
feedback. After that I will add test cases for travis-ci that test the
loadability of all the sql files.
On Mon, Sep 15, 2014 at 7:07 PM, Chris Travers
wrot
I made some additional fixes to this file (well beyond this release). I
will put out an rc-3 today
On Mon, Sep 15, 2014 at 4:23 PM, Chris Travers
wrote:
> I think I need to add some tests to Travis-CI that use
> PGObject::Util::DBAdmin to test the loadability of these files.
>
> We have much b
I think I need to add some tests to Travis-CI that use
PGObject::Util::DBAdmin to test the loadability of these files.
We have much better testing here on master and 1.4 than we do on 1.3
On Mon, Sep 15, 2014 at 10:47 AM, Michael Richardson
wrote:
>
> I tried 1.3.43rc2. I got past the empl
Hi Michael,
Thank you very much for your bugfix, I committed to the 1.3 branch, your name
in the commit:
https://github.com/ledgersmb/LedgerSMB/commit/18fbef39e4bd65cf03929a54a0c7854709e815d2
In fact, the 1.3 is pretty stable I think, there are a big number of fixes and
improvements.
I just
I tried 1.3.43rc2. I got past the employee__save, although I had
two ghost postgres accounts half-created that I should have cleaned up first.
I'll try again after dropping all the roles, but see the bottom of this email.
I then got, in the edit function of the main system, trying to clean stuff
Pongrácz István wrote:
> Is it a brand new installation? Or you entered to the existing DB and
> tried to add a new employee?
The machine is brand new.
Installed the debian package to get everything setup, move
/usr/share/ledgersmb (1.3.18) aside, and replaced it iwth 1.3.43rc1.
Then I
1.3.43-rc2 released to correct this problem. I don't foresee us releasing
1.3.43 before 1.4.0 is released at present.
Best Wishes,
Chris Travers
On Thu, Sep 11, 2014 at 5:53 PM, Chris Travers
wrote:
> So it looks like there is a significant improvement in our testing in 1.4
> compared to 1.3,
So it looks like there is a significant improvement in our testing in 1.4
compared to 1.3, where any db load issue is found and causes a test case
failure, while in 1.3, we don't have full db module coverage.
This is something we will definitely have to keep in mind when we see test
failures in 1.
ouch. patch applied.
I wonder if I accidently reverted a patch or why the Travis CI tests (which
do test db load btw) didn't fail.
On Thu, Sep 11, 2014 at 2:03 PM, Pongrácz István
wrote:
>
> I guess this is a brand new DB.
>
> Check this patch:
>
> diff -u Employee.sql Employee.sql-fixed
> ---
I guess this is a brand new DB.
Check this patch:
diff -u Employee.sql Employee.sql-fixed
--- Employee.sql2014-09-05 15:13:49.009844457 +0200
+++ Employee.sql-fixed 2014-09-11 22:58:12.264103592 +0200
@@ -9,7 +9,8 @@
DROP FUNCTION IF EXISTS employee__save
(in_entity_id int, in_start
Hi,
Is it a brand new installation?
Or you entered to the existing DB and tried to add a new employee?
Bye,
István
eredeti üzenet-
Feladó: "Michael Richardson" m...@sandelman.ca
Címzett: "Development discussion for LedgerSMB"
ledger-smb-devel@lists.sourcefor
The setup.pl, "Add User" function results in:
Error!
No such function: employee__save
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works| network architect [
] m...@sandelman.ca http://www.sandel
12 matches
Mail list logo
