Hi,

On 10/29/09 19:08, Andrew Jensen wrote:
Data!

Here is what I was thinking.

Option 1 - Just push the data into the odb file(s) and be done with it.
Pros - Doesn't get any easier then downloading one file.
Cons - The download is big.

Option 2 - refer users to the existing sakila data file at sourceforge and
add a macro in the odb file that reads the file (which is a bunch of insert
statements), perform any string replacements needed per line and execute
each against the curent connection.

The user would only need to download the Sakila data zip file, decompress it
to their local drives and run the macro - One dialog to get the location of
the file and that should be it.

Pros - The odb files are nice and small
Cons - Exrra download, Slow (then again that is a whole other question with
the embedded files)

Option 3 - ??

Anyhow - I was going to leave data for last, but perhaps it makes most sense
to it next and then the views and such afterwards.

Any thoughts - data next?
I would choose option 2, that wouldn't need any legal work on our side ;-) And such a sql script importer could be a nice extension for OOo.

- oj
Drew

On Thu, Oct 29, 2009 at 7:42 AM, Ocke Janssen <ocke.jans...@sun.com> wrote:

Hi Drew,

Thanks. Looks great. I just missing the data ;-)
In my test I used also the sakila schema with data and I figured out that
CLOBs are making trouble and the zip package (storing inside OOo) as well.
When inserting a clob value where a trigger is waiting for data inserting
like it is for the table film and film_text we have a dead lock. Fred from
hsqldb already as a look at it.

Off site: We need to support triggers at the UI ;-)

- oj



On 10/29/09 09:25, Drew Jensen wrote:

Then it must be time for frist test files

Attached are two files, both derived from the Sakila 0.8 data schema.

sakila-ooo-32-1028.odb
- Created w/ DEV320m_2 - tables, indexes and table constraints

sakila-hsqldb-1028-03a.odb
- Created w/ CWS build uploaded 10/28/2009 - tables, indexes, table
constraints and triggers (minus 1)
- domains (one with CHECK constraint)

3 forms in each file:

Schema-MySQL-5 (original Sakila 0.8 schema)

Schema-OOo-hsql-2-3.2 (the HSQLdb 1.8 schema)
-- All PK fields as integer identity
-- MySQL ENUM and SET data type replaced w/ CHAR and VARCHAR types
-- All FK relations from original schema
--- The database can be recreated by copy/paste of this file into the SQL
window in an empty Base 2.x file.

Schema-OOo-hsql-3.3 (the HSQLdb 1.9 schema)
-- PK fields defined with same data types as original schema
-- MySQL ENUM and SET data type replaced w custom domains
-- All but one upate / insert triggers
-- Stored procedure as first setp in supporting missing update trigger
upd_film from original schema
-- The database can not be recreated by a simple copy/paste of this file
into the SQL window of a Base file. (yet)

Views to follow.

By the way - forms are rather broken in that last build, it seems.

Later,

Drew



On Wed, Oct 28, 2009 at 2:53 AM, Ocke Janssen <ocke.jans...@sun.com<mailto:
ocke.jans...@sun.com>> wrote:

   Moin again,

   It's time for a new version.

   - oj


   On 10/21/09 15:08, Ocke Janssen wrote:

       Moin,

       I uploaded a new version. Please have a look at the cws
       hsqldb19 for fixed issues.

http://tools.services.openoffice.org/EIS2/cws.ShowCWS?Id=8774&logon=true&OpenOnly=false&Section=Tasks
       <
http://tools.services.openoffice.org/EIS2/cws.ShowCWS?Id=8774&logon=true&OpenOnly=false&Section=Tasks
If you file new issues please add them to the cws. Thanks.

       - oj

       On 10/14/09 15:12, Ocke Janssen wrote:

           Moin,

           I've uploaded a new version based on DEV300m61 with the
           new hsqldb version 1.9rc6 + patches.
           This is NO WORKING RELEASE, if your data is import then
           DON'T USE IT. ;-)

           For the people who want to start testing please work on
           copied data because the file format isn't backward
           compatible. Once converted can't be ported back. So test only.

           As I'm waiting for the first bug reports, I put a
           hsqldb.jar in the root of hsqldb19 every time a fix is
           available which has to be copied in the classes folder.

           So happy testing.

           Best regards,

           Ocke

           PS: The files can be found
           qa-upload.services.openoffice.org
           <http://qa-upload.services.openoffice.org> in the folder
           hsqldb19.






--
Ocke Janssen                      Tel: +49 40 23646 661, x66661
Dipl. Inf(FH)                     Fax: +49 40 23646 550
Sun Microsystems Inc.
Nagelsweg 55                      mailto:ocke.jans...@sun.com
D-20097 Hamburg                   http://www.sun.com/staroffice

Sitz der Gesellschaft:
Sun Microsystems GmbH, Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschaeftsfuehrer: Thomas Schr?der, Wolfgang Engels, Wolf Frenkel
Vorsitzender des Aufsichtsrates: Martin Haering


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org
For additional commands, e-mail: dev-h...@dba.openoffice.org

Reply via email to