gda crash in load_owner() with PostgreSQL backend

[Mark Johnson]

Graham Menhennitt wrote:
> Phil Longstaff wrote:
>   
>> Graham Menhennitt wrote:
>>   
>>     
>>> saved. I then try to load from the DB using a command line parameter of
>>> the DSN. It runs for a few seconds and then crashes with a segmentation
>>> violation. 
>>>     
>>>       
>> I just committed rev 16942 which should fix this.  I don't use the 
>> business objects, so please exercise them.   
>>     
>
> Yes, that fixed it, thanks. I still get a message when it starts saying
>     NOTICE: CREATE TABLE / PRIMARY KEY will create implicit index
> "billterms_pkey" for table "billterms"
> but my data seems to load correctly. Note that I don't actually have any
> billing terms in my data.
>
> I'll do some more testing.
>
> Thanks,
>     Graham
>
>   
The notice is normal PostgreSQL output.  It means that when you create a 
primary key, it implicitly creates an index.  I expect that the purpose 
of the message is to inform the user of the name of that index object, 
as the existence of the index to support the primary key is necessary.

Mark