| Summary: | opening mysql database crash | ||
|---|---|---|---|
| Product: | [Applications] KEXI | Reporter: | Bill Newton <spiderbill> |
| Component: | Migration/Import/Export | Assignee: | Kexi Bugs <kexi-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | adam, inksi, staniek |
| Priority: | NOR | Keywords: | drkonqi, triaged |
| Version: | 2.9.5 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | attachment-8028-0.html | ||
|
Description
Bill Newton
2015-08-18 13:59:33 UTC
@Bill Newton Thanks for the report. From the backtrace it looks like an issue with importing an existing externally-created MySQL database, not opening 'own' one. Knowing at least a schema of table that causes the bug would be a first step. You can send me it privately as a SQL dump if it's secret or attach below (preferred). Sometimes specific data is the factor. Finally, sometimes specific MySQL server configuration is the factor. See also A4.2 at http://kexi-project.org/wiki/wikiview/index.php@KexiFAQ.html#4._Database_Support_&_Data_Migration Created attachment 94208 [details] attachment-8028-0.html Hi Jarosław, Thanks for the quick response! Unfortunately, I'm prohibited by a NDA from sharing the schema. But, I might be able to reproduce it with a different schema that has some of the same traits. Cheers, Bill On Mon, Aug 24, 2015, 7:51 AM Jarosław Staniek <staniek@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=351444 > > Jarosław Staniek <staniek@kde.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC| |staniek@kde.org > > --- Comment #1 from Jarosław Staniek <staniek@kde.org> --- > @Bill Newton > Thanks for the report. > > From the backtrace it looks like an issue with importing an existing > externally-created MySQL database, not opening 'own' one. > > Knowing at least a schema of table that causes the bug would be a first > step. > You can send me it privately as a SQL dump if it's secret or attach below > (preferred). > > Sometimes specific data is the factor. > > Finally, sometimes specific MySQL server configuration is the factor. > > See also A4.2 at > > http://kexi-project.org/wiki/wikiview/index.php@KexiFAQ.html#4._Database_Support_&_Data_Migration > > -- > You are receiving this mail because: > You reported the bug. > But, I might be able to reproduce it with a different schema that has some of the same traits.
Thanks Bill, this would help.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |