Issue 39686 - crash when copying the bugdoc table
Summary: crash when copying the bugdoc table
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: 680m66
Hardware: All All
: P2 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: marc.neumann
QA Contact: issues@dba
Keywords: regression
Depends on:
Blocks: 19843
  Show dependency tree
Reported: 2004-12-30 08:24 UTC by Frank Schönheit
Modified: 2006-05-31 14:29 UTC (History)
1 user (show)

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

script to create the bug table (1.43 KB, text/plain)
2004-12-30 08:25 UTC, Frank Schönheit
no flags Details
stack of the crash (2.89 KB, text/plain)
2004-12-30 08:26 UTC, Frank Schönheit
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Frank Schönheit 2004-12-30 08:24:36 UTC
- import the attached SQL script into a MySQL database of your choice
- in OOo, create a database document for this MySQL database
  (I used MySQL/ODBC as connection type, but don't know whether this matters)
- open this database document
- View|Database objects|Tables
- select the table "i19843", and drag'n'drop it onto the "Tables" icon in the
left pane
=> the "Copy Table" wizard opens
- enter a table name which does not already exist in the database
- press "Create"
=> OOo crashs
Comment 1 Frank Schönheit 2004-12-30 08:25:21 UTC
Created attachment 20905 [details]
script to create the bug table
Comment 2 Frank Schönheit 2004-12-30 08:26:42 UTC
Created attachment 20906 [details]
stack of the crash
Comment 3 Frank Schönheit 2004-12-30 08:27:03 UTC
this used to work in some recent build -> keyword "regression"
Comment 4 ocke.janssen 2005-01-03 12:49:12 UTC
Fixed in cws dba22
Comment 5 ocke.janssen 2005-01-10 12:52:18 UTC
Reopen for QA
Comment 6 ocke.janssen 2005-01-10 12:53:40 UTC
Please verify. Thanks.
Comment 7 ocke.janssen 2005-01-10 12:53:58 UTC
Set to fix again
Comment 8 Frank Schönheit 2005-01-13 14:50:33 UTC
verified myself in agreement with MSC
Comment 9 marc.neumann 2005-04-26 12:09:04 UTC

fixed in current developer build -> close.
The current developer build can be found at
Feel free to reopen if this issue is not fixed in the developer build.

Bye Marc