On Sat, 2012-06-09 at 20:32 -0400, Chris Travers wrote:
> On Sat, Jun 9, 2012 at 10:03 AM, Robert James Clay wrote:
> > On Sat, 2012-06-09 at 12:28 -0400, Robert James Clay wrote:
> >> Decided to go ahead & try that but didn't get as far as checking the
> >> entity table. I tried commenting o
On Sat, Jun 9, 2012 at 10:03 AM, Robert James Clay wrote:
> On Sat, 2012-06-09 at 12:28 -0400, Robert James Clay wrote:
>> On Fri, 2012-06-08 at 21:36 -0400, Chris Travers wrote:
>> > I would comment out the check constraint on line 483 of the
>> > Pg-Database.sql and try again.
>> >
>> > Then I w
On Sat, 2012-06-09 at 12:28 -0400, Robert James Clay wrote:
> On Fri, 2012-06-08 at 21:36 -0400, Chris Travers wrote:
> > I would comment out the check constraint on line 483 of the
> > Pg-Database.sql and try again.
> >
> > Then I would look at the data in the entity table and see what might
> >
On Fri, 2012-06-08 at 21:36 -0400, Chris Travers wrote:
> I would comment out the check constraint on line 483 of the
> Pg-Database.sql and try again.
>
> Then I would look at the data in the entity table and see what might
> be throwing it.
Decided to go ahead & try that but didn't get as fa
On Fri, Jun 8, 2012 at 7:09 PM, Robert James Clay wrote:
> On Fri, 2012-06-08 at 21:36 -0400, Chris Travers wrote:
>> On Fri, Jun 8, 2012 at 11:45 AM, Robert James Clay wrote:
>> > On Thu, 2012-06-07 at 19:12 -0400, Chris Travers wrote:
>> >> On Thu, Jun 7, 2012 at 12:22 PM, Robert James Clay wr
On Fri, 2012-06-08 at 21:36 -0400, Chris Travers wrote:
> On Fri, Jun 8, 2012 at 11:45 AM, Robert James Clay wrote:
> > On Thu, 2012-06-07 at 19:12 -0400, Chris Travers wrote:
> >> On Thu, Jun 7, 2012 at 12:22 PM, Robert James Clay wrote:
> >> > On Thu, 2012-06-07 at 11:03 -0400, Chris Travers wr
]
On Fri, Jun 8, 2012 at 11:45 AM, Robert James Clay wrote:
> On Thu, 2012-06-07 at 19:12 -0400, Chris Travers wrote:
>> On Thu, Jun 7, 2012 at 12:22 PM, Robert James Clay wrote:
>> > On Thu, 2012-06-07 at 11:03 -0400, Chris Travers wrote:
>> >
>> >> Try this:
>> >>
>> >> select * from customer
On Thu, 2012-06-07 at 19:12 -0400, Chris Travers wrote:
> On Thu, Jun 7, 2012 at 12:22 PM, Robert James Clay wrote:
> > On Thu, 2012-06-07 at 11:03 -0400, Chris Travers wrote:
> >
> >> Try this:
> >>
> >> select * from customer where name !~ '[[:alnum:]_]'::text;
> >>
> >> and the same from vendo
On Thu, Jun 7, 2012 at 12:22 PM, Robert James Clay wrote:
> On Thu, 2012-06-07 at 11:03 -0400, Chris Travers wrote:
>
>> Try this:
>>
>> select * from customer where name !~ '[[:alnum:]_]'::text;
>>
>> and the same from vendor.
>
> Both returns zero rows...
And just to be sure, selecting count
On Thu, 2012-06-07 at 11:03 -0400, Chris Travers wrote:
> Try this:
>
> select * from customer where name !~ '[[:alnum:]_]'::text;
>
> and the same from vendor.
Both returns zero rows...
Jame
--
Live Secur
On Thu, Jun 7, 2012 at 7:33 AM, Robert James Clay wrote:
> On Tue, 2012-06-05 at 22:31 -0400, Chris Travers wrote:
>> On Tue, Jun 5, 2012 at 10:49 AM, Robert James Clay wrote:
>> > On Mon, 2012-06-04 at 15:14 -0400, Robert James Clay wrote:
>
>> > The issue I'm seeing now on the test db is
On Tue, 2012-06-05 at 22:31 -0400, Chris Travers wrote:
> On Tue, Jun 5, 2012 at 10:49 AM, Robert James Clay wrote:
> > On Mon, 2012-06-04 at 15:14 -0400, Robert James Clay wrote:
> > The issue I'm seeing now on the test db is that the
> > conversion is failing with the following error (1.3
On Tue, Jun 5, 2012 at 10:49 AM, Robert James Clay wrote:
> On Mon, 2012-06-04 at 15:14 -0400, Robert James Clay wrote:
>> On Sun, 2012-06-03 at 19:59 -0400, Chris Travers wrote:
>> > I was looking into this. It looks like Erik committed a fix for this
>> > issue for 1.3.16.
>>
>> However,
On Tue, 2012-06-05 at 02:39 -0400, Jos Geluk wrote:
> Robert James Clay schreef op 05-06-12 00:34:
> > On Sun, 2012-06-03 at 19:15 -0400, Jos Geluk wrote:
> >> Robert James Clay schreef op 03-06-12 23:40:
> After the error above, I installed the .deb file over it,
> >>>
> >>> The 1.3.15-
On Mon, 2012-06-04 at 15:14 -0400, Robert James Clay wrote:
> On Sun, 2012-06-03 at 19:59 -0400, Chris Travers wrote:
> > I was looking into this. It looks like Erik committed a fix for this
> > issue for 1.3.16.
>
> However, the resulting database does not have the company data that
> sh
On Mon, Jun 4, 2012 at 11:52 PM, Chris Travers wrote:
> After you run the downgrade script.
Then you can install the hotfix and try again.
Best Wishes,
Chris Travers
--
Live Security Virtual Conference
Exclusive live e
On Mon, Jun 4, 2012 at 11:39 PM, Jos Geluk wrote:
> Robert James Clay schreef op 05-06-12 00:34:
>> On Sun, 2012-06-03 at 19:15 -0400, Jos Geluk wrote:
>>> Robert James Clay schreef op 03-06-12 23:40:
> After the error above, I installed the .deb file over it,
The 1.3.15-2 pack
Robert James Clay schreef op 05-06-12 00:34:
> On Sun, 2012-06-03 at 19:15 -0400, Jos Geluk wrote:
>> Robert James Clay schreef op 03-06-12 23:40:
After the error above, I installed the .deb file over it,
>>>
>>> The 1.3.15-2 package from the Debian repository? And over what kind
>>> of
On Sun, 2012-06-03 at 19:15 -0400, Jos Geluk wrote:
> Robert James Clay schreef op 03-06-12 23:40:
> >> After the error above, I installed the .deb file over it,
> >
> > The 1.3.15-2 package from the Debian repository? And over what kind
> > of previous installation?
>
> Yes, from
> http://f
On Sun, 2012-06-03 at 19:59 -0400, Chris Travers wrote:
> I was looking into this. It looks like Erik committed a fix for this
> issue for 1.3.16.
That quite likely did take care of the LedgerSMB/Template/TXT.pm
related errors: I was able to duplicate those errors using a test v1.2
database
If anyone needs a hotfix, grab the latest LedgerSMB/Template/TXT.pm at
https://ledger-smb.svn.sourceforge.net/svnroot/ledger-smb/branches/1.3/LedgerSMB/Template/TXT.pm
This is the only change afaics that has been made to this file since 1.3.15.
Best Wishes,
Chris Travers
On Sun, Jun 3, 2012 at 4:15 PM, Jos Geluk wrote:
> Robert James Clay schreef op 03-06-12 23:40:
>
>>> No, I haven't got it to work yet. I would be grateful if you could point
>>> me to that particular bug.
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675816
>
> Thank you.
> I notice that
Robert James Clay schreef op 03-06-12 23:40:
>> No, I haven't got it to work yet. I would be grateful if you could point
>> me to that particular bug.
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675816
Thank you.
I notice that the bug reporter hints to the httpd.conf file, which was
emp
On Sun, 2012-06-03 at 16:15 -0400, Jos Geluk wrote:
> Robert James Clay schreef op 03-06-12 20:48:
> > On Fri, 2012-04-13 at 09:05 -0400, Jos Geluk wrote:
> >>
> >> syntax error at LedgerSMB/Template/TXT.pm line 116, near "'.'
> >> get_extension"
> >> Compilation failed in require at (eval 10
Robert James Clay schreef op 03-06-12 20:48:
> Jos,
>
> On Fri, 2012-04-13 at 09:05 -0400, Jos Geluk wrote:
>
>> So I tried with 1.3.15RC2 but didn't even get as far as that: I got an
>> Apache error saying:
>>
>> commit ineffective with AutoCommit enabled at scripts/setup.pl line 519.
>> Bareword
Jos,
On Fri, 2012-04-13 at 09:05 -0400, Jos Geluk wrote:
> So I tried with 1.3.15RC2 but didn't even get as far as that: I got an
> Apache error saying:
>
> commit ineffective with AutoCommit enabled at scripts/setup.pl line 519.
> Bareword found where operator expected at LedgerSMB/Template/TX
Oh. LSMB 1.3.16 and PostgreSQL 9.1.3.
On Tue, May 8, 2012 at 8:50 AM, M Lubratt wrote:
> Hello. I'm having the exact same issue with one of my databases. One of
> the curious things is that I have 2 other databases on the same PostgreSQL
> cluster that don't exhibit this problem. Has anyone
Hello. I'm having the exact same issue with one of my databases. One of
the curious things is that I have 2 other databases on the same PostgreSQL
cluster that don't exhibit this problem. Has anyone solved this issue?
Thanks!
Mark
Chris Travers wrote op 13-04-12 11:45:
> On Fri, Apr 13, 2012 at 2:33 AM, Jos Geluk wrote:
>> Chris Travers wrote:
>>
>>> I believe some of these may have been fixed in 1.3.15.
>>
>> Thanks. Can you be more specific as to what "some of these" mean? (I'm
>> practically debugging the SQL at this poi
RC2 is out now btw.
Best Wishes,
Chris Travers
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.ne
On Fri, Apr 13, 2012 at 2:33 AM, Jos Geluk wrote:
> Chris Travers wrote:
>
>> I believe some of these may have been fixed in 1.3.15.
>
> Thanks. Can you be more specific as to what "some of these" mean? (I'm
> practically debugging the SQL at this point.)
Hmmm in double checking I found a couple
Chris Travers wrote:
> I believe some of these may have been fixed in 1.3.15.
Thanks. Can you be more specific as to what "some of these" mean? (I'm
practically debugging the SQL at this point.)
> I am curious as to how our reconciliation foreign exchange tests
> passed if the reconciliation mo
Hi;
I believe some of these may have been fixed in 1.3.15.
I am curious as to how our reconciliation foreign exchange tests
passed if the reconciliation module wasn't reloading properly though.
Best Wishes,
Chris Travers
--
I'm sorry to insist but I am getting no further with converting my
1.2.25 database. I have repeatedly wiped the Ledgersmb installation,
reinstalled Ledgersmb, wiped the database and reloaded the old database.
Each time, when running setup.pl, it takes me through the steps:
entering superuser cr
Erik Huelsmann wrote:
> Could you try with version 1.3.14? At some stage the excess LANGUAGE
> PLPGSQL has been removed on the 1.3 branch and it's no longer in 1.3.14
> which should solve at least that problem.
Thank you for replying, but no, this doesn't help. I get a slightly
different set of
Hi Jos,
On Mon, Apr 9, 2012 at 8:39 PM, Jos Geluk wrote:
> While upgrading a test database from 1.2.25 to 1.3.10, I am able to log
> in as a user. However, after the upgrade, the database does not contain
> any actual data.
> When using psql I see that AR, AP, OE etc have 0 rows. The statement
>
While upgrading a test database from 1.2.25 to 1.3.10, I am able to log
in as a user. However, after the upgrade, the database does not contain
any actual data.
When using psql I see that AR, AP, OE etc have 0 rows. The statement
SELECT * FROM defaults WHERE setting_key = 'version'
shows me that
I should have added that I am using PostgreSQL 9.1 on Ubuntu 11.10, Perl
5.12.4.
Jos.
--
www.ardispark.nl
tel. 06 5341 4670
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
38 matches
Mail list logo
