On 11/01/2012 10:29, Nigel Titley wrote:
> On 11/01/2012 06:14, Chris Travers wrote:
>> You have a contact where you have a duplicate email address (email,
>> bcc, cc). Is there a legitimate use case where you would want to send
>> an email to someone and at the same time cc/bcc the same address (
On 11/01/2012 10:38, Chris Travers wrote:
> Yep. As failures are found the pre-validation tests need to be add,
> where we missed something. However, if it is OK with you I would like
> to get you migrated first and then figure out what checks need to be
> added.
That is fine... we are doing thi
On Wed, Jan 11, 2012 at 2:29 AM, Nigel Titley wrote:
> On 11/01/2012 06:14, Chris Travers wrote:
>> On Tue, Jan 10, 2012 at 2:56 PM, Nigel Titley wrote:
>>> On 10/01/12 22:02, Erik Huelsmann wrote:
Hi Nigel,
> I'm about to add a header at the start, dump a new test copy of the
> data
On 11/01/2012 06:14, Chris Travers wrote:
> On Tue, Jan 10, 2012 at 2:56 PM, Nigel Titley wrote:
>> On 10/01/12 22:02, Erik Huelsmann wrote:
>>> Hi Nigel,
I'm about to add a header at the start, dump a new test copy of the
database and try again.
>>> That should do it. Please let us know
On Tue, Jan 10, 2012 at 2:56 PM, Nigel Titley wrote:
> On 10/01/12 22:02, Erik Huelsmann wrote:
>> Hi Nigel,
>
>>> I'm about to add a header at the start, dump a new test copy of the
>>> database and try again.
>>
>> That should do it. Please let us know about your outcome.
>
> OK, I'm now getting
On 10/01/12 22:02, Erik Huelsmann wrote:
> Hi Nigel,
>> I'm about to add a header at the start, dump a new test copy of the
>> database and try again.
>
> That should do it. Please let us know about your outcome.
OK, I'm now getting a little further on
psql:1.2-1.3-upgrade.sql:38: ERROR: null
Hi Nigel,
On Tue, Jan 10, 2012 at 10:43 PM, Nigel Titley wrote:
> On 09/01/12 20:11, Erik Huelsmann wrote:
>> Hi Nigel,
>>
>> Many thanks... I'll work through and find out which account is causing
>> the problem.
>>
> Hmm, this fails at the first fence, with offset 0. I think its
On 09/01/12 20:11, Erik Huelsmann wrote:
> Hi Nigel,
>
> Many thanks... I'll work through and find out which account is causing
> the problem.
>
Hmm, this fails at the first fence, with offset 0. I think its a more
fundamental error with the "account_save" procedure.
>>>
On 09/01/2012 19:49, Erik Huelsmann wrote:
> Hi Nigel,
>
Many thanks... I'll work through and find out which account is causing
the problem.
>>> Hmm, this fails at the first fence, with offset 0. I think its a more
>>> fundamental error with the "account_save" procedure.
>>>
>> I'm s
On 10/01/2012 09:08, Chris Travers wrote:
> Sorry for the delay. I have been on vacation.
Really no problem, hope you had a good time.
>
> No doesn't seem to have made any difference. Still the same error
>
> psql:/tmp/ledgersmb/1.2-1.3-upgrade.sql:30: ERROR: null value in column
> "heading" viol
Sorry for the delay. I have been on vacation.
On Sat, Dec 31, 2011 at 9:31 AM, Nigel Titley wrote:
> On 31/12/11 15:40, Nigel Titley wrote:
>> On 31/12/11 11:26, Nigel Titley wrote:
>>> On 31/12/11 10:23, Nigel Titley wrote:
On 31/12/11 09:50, Chris Travers wrote:
> Ok now we are g
Hi Nigel,
Many thanks... I'll work through and find out which account is causing
the problem.
>>> Hmm, this fails at the first fence, with offset 0. I think its a more
>>> fundamental error with the "account_save" procedure.
>>>
>> I'm still no further forward with this. Can someone
Hi Nigel,
>>> Many thanks... I'll work through and find out which account is causing
>>> the problem.
>>>
>> Hmm, this fails at the first fence, with offset 0. I think its a more
>> fundamental error with the "account_save" procedure.
>>
> I'm still no further forward with this. Can someone put me
On 04/01/2012 15:52, Nigel Titley wrote:
> On 04/01/12 15:43, Nigel Titley wrote:
>> On 03/01/12 18:27, Michael Richardson wrote:
"Nigel" == Nigel Titley writes:
>>> >> No doesn't seem to have made any difference. Still the same error
>>> >>
>>> >> psql:/tmp/ledgersmb/1.2
On 04/01/12 15:43, Nigel Titley wrote:
> On 03/01/12 18:27, Michael Richardson wrote:
>>> "Nigel" == Nigel Titley writes:
>> >> No doesn't seem to have made any difference. Still the same error
>> >>
>> >> psql:/tmp/ledgersmb/1.2-1.3-upgrade.sql:30: ERROR: null value in
>> >>
On 03/01/12 18:27, Michael Richardson wrote:
>> "Nigel" == Nigel Titley writes:
> >> No doesn't seem to have made any difference. Still the same error
> >>
> >> psql:/tmp/ledgersmb/1.2-1.3-upgrade.sql:30: ERROR: null value in
> >> column "heading" violates not-null constraint
> "Nigel" == Nigel Titley writes:
>> No doesn't seem to have made any difference. Still the same error
>>
>> psql:/tmp/ledgersmb/1.2-1.3-upgrade.sql:30: ERROR: null value in
>> column "heading" violates not-null constraint CONTEXT: SQL
>> statement "INSERT INTO account (a
On 31/12/11 17:31, Nigel Titley wrote:
> On 31/12/11 15:40, Nigel Titley wrote:
>> On 31/12/11 11:26, Nigel Titley wrote:
>>> On 31/12/11 10:23, Nigel Titley wrote:
On 31/12/11 09:50, Chris Travers wrote:
> Ok now we are getting somewhere.
>
> What username are you using to se
On 31/12/11 15:40, Nigel Titley wrote:
> On 31/12/11 11:26, Nigel Titley wrote:
>> On 31/12/11 10:23, Nigel Titley wrote:
>>> On 31/12/11 09:50, Chris Travers wrote:
>>>
Ok now we are getting somewhere.
What username are you using to set up the database? It must be a
database s
On 31/12/11 11:26, Nigel Titley wrote:
> On 31/12/11 10:23, Nigel Titley wrote:
>> On 31/12/11 09:50, Chris Travers wrote:
>>
>>> Ok now we are getting somewhere.
>>>
>>> What username are you using to set up the database? It must be a
>>> database superuser.
>>
>> I was using postgres. However, I
On 31/12/11 10:23, Nigel Titley wrote:
> On 31/12/11 09:50, Chris Travers wrote:
>
>> Ok now we are getting somewhere.
>>
>> What username are you using to set up the database? It must be a
>> database superuser.
>
> I was using postgres. However, I've now added "create database"
> privilege to
On 31/12/11 09:50, Chris Travers wrote:
> Ok now we are getting somewhere.
>
> What username are you using to set up the database? It must be a
> database superuser.
I was using postgres. However, I've now added "create database"
privilege to the ledgersmb user and the process has largely gone
On Sat, Dec 31, 2011 at 12:44 AM, Nigel Titley wrote:
> On 31/12/11 02:20, Chris Travers wrote:
>> Check the /tmp/ledgersmb/dblog_stderr for the error.
>
> psql:sql/Pg-database.sql:2: ERROR: syntax error at or near "EXTENSION"
> LINE 1: CREATE EXTENSION tablefunc;
> ^
> psql:sql/Pg-
On 31/12/11 08:44, Nigel Titley wrote:
> On 31/12/11 02:20, Chris Travers wrote:
>> Check the /tmp/ledgersmb/dblog_stderr for the error.
>
> psql:sql/Pg-database.sql:2: ERROR: syntax error at or near "EXTENSION"
> LINE 1: CREATE EXTENSION tablefunc;
>^
> psql:sql/Pg-database.sql:3
On 31/12/11 02:20, Chris Travers wrote:
> Check the /tmp/ledgersmb/dblog_stderr for the error.
psql:sql/Pg-database.sql:2: ERROR: syntax error at or near "EXTENSION"
LINE 1: CREATE EXTENSION tablefunc;
^
psql:sql/Pg-database.sql:3: ERROR: syntax error at or near "EXTENSION"
LINE 1
Check the /tmp/ledgersmb/dblog_stderr for the error.
Best Wishes,
Chris Travers
--
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure
On 30/12/11 23:36, Nigel Titley wrote:
> On 30/12/11 23:03, [email protected] wrote:
>> Hi nigel,
>>
>> this is a known issue: your server doesn't have the postgresql contribs or
>> they didn't get imported in your db. If you use setup.pl, be sure the path
>> in ledgersmb.conf points to the right
On 30/12/11 23:03, [email protected] wrote:
> Hi nigel,
>
> this is a known issue: your server doesn't have the postgresql contribs or
> they didn't get imported in your db. If you use setup.pl, be sure the path in
> ledgersmb.conf points to the right dir (9.0 or below).
I have postgresql contri
-
From: Nigel Titley
Sent: 30/12/2011, 23:49
To: Development discussion for LedgerSMB
Subject: [Ledger-smb-devel] Error when upgrading 1.2 db to 1.3 db
Testing the upgrade 1.2 to 1.3 functionality I get the following error
Error!
42883:ERROR: function public.person__list_salutations() does not
On 30/12/11 22:49, Nigel Titley wrote:
> Testing the upgrade 1.2 to 1.3 functionality I get the following error
>
> Error!
>
> 42883:ERROR: function public.person__list_salutations() does not exist
> LINE 1: SELECT * FROM "public"."person__list_salutations"() ^ HINT: No
> function matches the giv
Testing the upgrade 1.2 to 1.3 functionality I get the following error
Error!
42883:ERROR: function public.person__list_salutations() does not exist
LINE 1: SELECT * FROM "public"."person__list_salutations"() ^ HINT: No
function matches the given name and argument types. You might need to
add exp
31 matches
Mail list logo
