Re: [dba-dev] HSQLDB 1.9 Testing needed
Hi Ocke, Ocke Janssen írta: Moin, On 10/15/09 19:49, Reizinger Zoltán wrote: Drew Jensen írta: Ocke Janssen wrote: On 10/15/09 11:32, Reizinger Zoltán wrote: Ocke Janssen írta: Win upload now completed and tested. I down loaded the new installation set, installed on winXP Home Hungarian version, from cmd window: msiexec/a openofficeorg32.msi into C:\Program Files\OOo_hsqldb19\ folder, installs without any problem. I changed bootstrap.ini, UserInstallation=$ORIGIN/.. soffice not starts from file manager, error mesage: (fast translation) Hi Zoltan, Just a thought - if a reinstall did not help then I would look immediately to the user configuration data. Befrore starting OO.o again be sure to double check the entry in the bootstrap.ini file Ensure that it is going to point to a non-existent (or verified empty) directory. I did it no change the problem, changed installation directory, installed into other drive, same error. I stopped installations, something other problem can cause this. I installed similar way the OOO320_m1, and DEV300_m61. Only change was from that time, windows update in this Tuesday. I give up on win version. The Windows version is non-product build where more assertions are visible as you would see in other cases. http://wiki.services.openoffice.org/wiki/Non_Product_Build It says that all debug messages should be submitted as issue, with ASSERT: in summary. What to do if I found one or more such assertions, in CWS hsqldb19. Create screenshot and put it to wiki page as Drew did, or submit issue? For the Windows build you need debug dll which aren't on your system by default. The link http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide/Building_on_Windows#software_requirements might help you to find the pieces which are missing. I hope that is a little help. I'm currently build a product version but for testing the non-product would be better. That's my personal opinion. After I installed Visual C++2008 Express Edition, I can start OOo, and start tests on winXP, Zoltan - oj - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] HSQLDB 1.9 Testing needed
Reizinger Zoltán wrote: Hi Ocke, Ocke Janssen írta: Moin, On 10/15/09 19:49, Reizinger Zoltán wrote: Drew Jensen írta: Ocke Janssen wrote: On 10/15/09 11:32, Reizinger Zoltán wrote: Ocke Janssen írta: Win upload now completed and tested. I down loaded the new installation set, installed on winXP Home Hungarian version, from cmd window: msiexec/a openofficeorg32.msi into C:\Program Files\OOo_hsqldb19\ folder, installs without any problem. I changed bootstrap.ini, UserInstallation=$ORIGIN/.. soffice not starts from file manager, error mesage: (fast translation) Hi Zoltan, Just a thought - if a reinstall did not help then I would look immediately to the user configuration data. Befrore starting OO.o again be sure to double check the entry in the bootstrap.ini file Ensure that it is going to point to a non-existent (or verified empty) directory. I did it no change the problem, changed installation directory, installed into other drive, same error. I stopped installations, something other problem can cause this. I installed similar way the OOO320_m1, and DEV300_m61. Only change was from that time, windows update in this Tuesday. I give up on win version. The Windows version is non-product build where more assertions are visible as you would see in other cases. http://wiki.services.openoffice.org/wiki/Non_Product_Build It says that all debug messages should be submitted as issue, with ASSERT: in summary. What to do if I found one or more such assertions, in CWS hsqldb19. Create screenshot and put it to wiki page as Drew did, or submit issue? Hi Zoltan, Actually I'll be, most likely, opening issues also - not just updating the wiki page. The wiki page, I'm hoping will serve a different purpose - to be able to go back through the page and generate one or more test scenarios. I'm trying to document each interaction (create something, alter something) and as I do assign it to the functional section it is testing. With the number of assertions/errors/warings being displayed to screen however I need to 1) start some issues 2) break the wiki page down into sub-pages for the different functional areas..else, I'm going to be lost pretty quick. ALSO @Ocke, or ?: Using the 10/16/09 CWSHsql19 build I get lots of errors in things that are not directly related to Base/HSQL or even Base. For instance trying to install the XRay macro via the distribution writer file found at OOoMacros.org. Under this build opening the pre-2.0 writer file generates a flurry of errors - but does open - trying to run the macro that installs XRay generates even more errors, then hangs the system and the XRay basic library is NOT copied into the system. Do I chaulk this up to the odd build, or report this in the issue tracker under framework? Drew - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
[dba-dev] 1.9 feature support? was ( HSQLDB 1.9 Testing needed )
Ok - how much of the new features in 1.9 should be usable in Base. I don't mean via the GUI, rather - Is there anything in the engine that is being suppressed in the embedded implementation? - Triggers , Procedures/Functions, etc How about the other way - Anything that under 3.2 was not available that will be in 3.3 (HSQL1.9)? For instance - I've created a couple of tables and added indexes, FKs via SQL window, works fine. Tried to add a trigger and...well, not quite working. 1) Create the table, indexes and trigger directly one after the other in the SQL window: -- Base accepts each command -- Can add/delete/edit data -- Trigger does not function/but doesn't generate an error either (ok, probably me and the trigger def. being wrong at this point...) -- Close file -- HSQLdb engine will not start on next open, the CREATE TRIGGER statement generated in the script file is the rejected command 2) Create the table, indexe in the SQL window: -- Base accepts -- Can add/edit/delete data -- Close file -- Open and there is no problem -- Run save CREATE TRIGGER statement as used in (1) above and it is rejected due to a RIGHTS violation in the engine. Right now then I'll go check the trigger statement against a stand alone HSQLdb engine...and then maybe use the HSQLdb supplied sample for triggers in the Base file (Table and Trigger def). But - before I get to far into these newer features just wanted to be sure that they are actually expected to work - meaning that they aren't be turned off in the implementation here. Thanks Drew - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] HSQLDB 1.9 Testing needed
Just a quick note: Updated these pages on the wiki http://wiki.services.openoffice.org/wiki/User:DrewJensen/HSQLdb/TestDB http://wiki.services.openoffice.org/wiki/User:DrewJensen/HSQLdb/1.9QATest/Wizard (errr, misnamed that page...I sometimes don't like MediaWiki very much ) Cached table for default - does seem that the new build simply is not adding the 'set database default table type cached' line in the script on NEW. Adding it via the SQL window as the first thing you do after creating a new Base file then creates cached tables via the GUI. Triggers - actually this whole new access privilege model, with roles, is rather interesting... anyway, does look like just needing to explicitly grant a role as a separate statement in the SQl window first... Drew - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
[dba-dev] change to auto_commit behavior in SQL window ( was : Re: 1.9 feature support? )
Thought I'd pass this along - When you are running multiple SQL statements in the SQL window how the auto_commit setting behaves has changed w/current 1.9 build. Under OO.o 3.2 (hsql 1.8) each statement is committed as executed. Under DEV 3.3 (hsql 1.9) the statements are committed or rolled back as a batch. To me this is much preferred as I can take control and force commits in a script if it needs to be broken down into smaller atomic pieces, there was *no* way to change the behavior of one statement / commit before. Drew - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
