Issue 8971 - Segmentation fault when saving newly created PostgreSQL table
Summary: Segmentation fault when saving newly created PostgreSQL table
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Linux, all
: P1 (highest) Trivial (vote)
Target Milestone: ---
Assignee: Frank Schönheit
QA Contact: issues@dba
URL:
Keywords:
: 9020 (view as issue list)
Depends on:
Blocks:
 
Reported: 2002-11-04 18:45 UTC by sophia
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description sophia 2002-11-04 18:45:16 UTC
I use OpenWriter 1.0.1 with the data source display.
I am connected to a PostgreSQL 7.2.2 database
throught unixODBC 2.2.2.

I use the 'new sketch of a table' wizard
to create a new table.
But each time I save it on the end,
then OpenOffice crashes with the lonly
error message in the console:
'Segmentation fault'.
When I reopen OpenWriter,
my new table has been created
with the right fields.
Comment 1 Frank Schönheit 2002-11-05 08:59:16 UTC
Sophia, thanks for using and supporting OpenOffice.org.

I have a dumb question: what is the "new sketch of a table" wizard?
Comment 2 sophia 2002-11-05 09:16:11 UTC
Sorry, I tried to translate as "new sketch of a table"
the french expression "Nouvelle ébauche de table".
This entry offers a form which helps
to define a new table.

This menu entry is accessed
in the data sources explorer (tree on the left)
by right clicking on the 'Table' node.
Comment 3 Frank Schönheit 2002-11-05 09:23:35 UTC
ah! :) You used the form auto pilot (translated from the german
version :) on a table, didn't you?
But you are creating a form document, not a table, am I right?

Does the same happen with other data source( type)s? For instance the
Bibliography?
Comment 4 sophia 2002-11-05 09:46:26 UTC
a/
No, I didn't used the form auto pilot
but the table auto pilot
in which I used a form
to define the fields of the table.


b/
This crash does not append
with the 'Bibliography' database.

My database is not crashed
because I can restart OpenOffice Writer
and fully access to my database
without restarting it.
The last messages that PostgreSQL logged were:
NOTICE:  CREATE TABLE / PRIMARY KEY will create implicit index
'essai4_pkey' for table 'essai4'
DEBUG:  pq_recvbuf: unexpected EOF on client connection
Comment 5 Frank Schönheit 2002-11-05 12:12:59 UTC
Sophia,
I admit I am heavily confused - there is no such thing as an auto
pilot for a table - at least not to my knowledge, except somebody
built such a piece of software specially for the french version (which
I doubt)

What I (this time :) suppose is that you mean the "normal" table
design component, means the component which is used when editing an
existent as well as when creating a new one.
Yes?
(I now strongly suppose so. I looked into the source, and "Nouvelle
ébauche de ~table" is the french translation of "New ~Table Design")
Comment 6 sophia 2002-11-05 12:39:03 UTC
Yes, that's right.
Comment 7 Frank Schönheit 2002-11-05 15:26:23 UTC
Ah! Okay, at least I understand what this is about :). Thanks Sophia!

changing the summary from
  Segmentation fault when saving new table created with the wizard
to
  Segmentation fault when saving newly created PostgreSQL table
'cause the "wizard" in the old summary is somewhat misleading.

Sophia, sorry, I have some more questions (:
* What table structure do you use when creating the new table?
* Does the crash _depend_ on the table structure? Does it happen no
matter what field types you use, and/or no matter how may fields you
use? Can you please try to strip down this to a table as simple as
possible?
Comment 8 sophia 2002-11-05 22:16:35 UTC
The bug still exist
if I use the SQL console of OpenOffice
(right click on the data source node -> 'SQL...').
I just executed the following SQL instruction:
CREATE TABLE a (a INTEGER PRIMARY KEY );

I also got the same result with other types:
VARCHAR
DATE
Comment 9 ocke.janssen 2002-11-13 10:10:15 UTC
Hi Sophia,

this bug is fixed now. I didn't test if it is already in the srx643
developer version but it should be in the next release.

Best regards,
Ocke
Comment 10 ocke.janssen 2002-12-12 14:52:50 UTC
*** Issue 9020 has been marked as a duplicate of this issue. ***
Comment 11 Frank Schönheit 2003-05-20 11:39:16 UTC
closing
Comment 12 hans_werner67 2004-02-02 12:59:14 UTC
change subcomponent to 'none'