[dba-issues] [Issue 115420] Base: NULL date import br eaks type recognition crashes OOo 3.3.0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115420 --- Additional comments from o...@openoffice.org Mon Dec 13 14:02:07 + 2010 --- The problem is that the 2nd column in the spreadsheet is formatted as Number. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 115420] Base: NULL date import br eaks type recognition crashes OOo 3.3.0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115420 User oj changed the following: What|Old value |New value Assigned to|dbaneedsconfirm |oj Ever confirmed| |1 Status|UNCONFIRMED |NEW Target milestone|--- |OOo 3.4 --- Additional comments from o...@openoffice.org Mon Dec 13 13:59:15 + 2010 --- Grabbing - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 115420] Base: NULL date import br eaks type recognition crashes OOo 3.3.0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115420 User oj changed the following: What|Old value |New value Status|NEW |RESOLVED Resolution| |FIXED --- Additional comments from o...@openoffice.org Mon Dec 13 14:01:00 + 2010 --- Fixed in cws dba34c. I fixed the recognation of the type. Desc is now a varchar. I couldn't reproduce the crash. Seems to fixed when the recognation was fixed. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 115420] Base: NULL date import br eaks type recognition crashes OOo 3.3.0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115420 --- Additional comments from atjen...@openoffice.org Mon Nov 22 08:17:07 + 2010 --- @yutgor - following your steps I can reproduce the erroneous import. (but not with the OO.o RC5 so someone else will need to do that to be sure) It is actually not the data that is corrupt but there is an error, in the GUI default format property for the table, as you describe. To see that it is not the data that is corrupt. Download the ODB file i115420, attached here. The file has two tables, Table7 and Table8 - these are created from your example .ods file, with the Memo data type. Table7 appears to have correct data and Table8 incorrect. To Fix Table8, you must do ALL of this Open Table8 definition for edit. Select the Desc field Click on the button to the right of the Format example In this dialog you must clear the ERROR by 1 - change to any user defined value - i.e. '@@' 2 - change back to the correct defaut for text '@' Save the table definition. Correct data is there. So the error is right at that format variable... Finally - I used on Linux, so no comment on the crash part of this only the problem with the display after import. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 115420] Base: NULL date import br eaks type recognition crashes OOo 3.3.0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115420 --- Additional comments from atjen...@openoffice.org Mon Nov 22 08:19:32 + 2010 --- Created an attachment (id=75084) Table8 has data directly after import from test ODS file - with bad display variable - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 115420] Base: NULL date import br eaks type recognition crashes OOo 3.3.0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115420 --- Additional comments from yut...@openoffice.org Tue Nov 23 01:43:47 + 2010 --- @atjensen: Thank you for confirming the defect at least on the Linux side. I downloaded your odb , as expected, OOo (330m15) crashed on opening the table since my OS is Win XP Pro. After OOo recovered, correct data could be displayed by following your steps (though they are quite non-trivial ;) Which build(s) did you test in on? Is there by any chance you could test it on 330m15 as well or ask someone to do so? - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 115420] Base: NULL date import br eaks type recognition crashes OOo 3.3.0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115420 User yutgor changed the following: What|Old value |New value Status|CLOSED|UNCONFIRMED Resolution|INVALID | Summary|Base: NULL date import bre|Base: NULL date import bre |aks type recognition may|aks type recognition cra | crash OOo 3.3.0 RC3 |shes OOo 3.3.0 --- Additional comments from yut...@openoffice.org Mon Nov 22 06:07:02 + 2010 --- @dbaneedsconfirm: Pls. cc some more people beside r4zoli to look at this issue. @r4zoli: PLEASE! Pls. don't just say this is invalid! Wasn't it you who said, If I use default settings (line max 10), and press Auto, the Desc recognized wrongly as Date The Format example is '1900-01-01'? You yourself have already confirmed 2 wrong behaviours this bug manifests you're now closing the issue as invalid??? What kind of service is this??? If you have difficulty understanding what's going on, pls. forward it to your team lead. We simply cannot leave such a defect, which may crash OOo in some cases, unaddressed. If we do, we're just inviting the public to use MS Office instead. And pls. specify what *exactly* you could not reproduce: corrupt data, crash, or both? For me, I can reproduce everything even in the *latest* build, OOO330m15, on 32-bit English Windows XP Pro SP3 (as well as in the *latest official* build, 320m19, on Ubuntu 10.10 in Oracle VM VirtualBox 3.2.10 r66523 on 32-bit English Windows XP Professional SP3--minus the crash since it's a Linux environment). Specifically, after clicking 'Auto', manually changing the field type of 'Desc' to Memo (yes, *Memo*, not Text), creating the table, when you open the table, the data in the 'Desc' column are corrupt OOo comes to a short freeze then crashes! FYI, I'm attaching the crash error report here (b-crash-import-null_date-report.xml). OOo appears to crash in getMsFromTime in dbtoolsmi.dll. Pls. have someone with the knowledge to look at it. BTW, have you looked into Issue #11308 yet? As noted, fixing that will likely change the behaviour of the current defect such that failure will occur on data row /x/ instead of /x/+1. Again, if you're unable to reproduce whatever phenomena, PLEASE forward to another developer or your team lead for further testing. Right now only 2 people have tested so far 1 person can reproduce it in multiple builds OS--actually a colleague helped in testing one of the builds/OS so you may even consider that as 2 people-- 1 can't. We really cannot say the issue is invalid w/o having at least one more person to test the case. So PLEASE ask some more people to look at it. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
[dba-issues] [Issue 115420] Base: NULL date import br eaks type recognition crashes OOo 3.3.0
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=115420 --- Additional comments from yut...@openoffice.org Mon Nov 22 06:09:09 + 2010 --- Created an attachment (id=75083) Crash Report - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org
