db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5437) Load all toursdb tables in one invocation of ij
Date Thu, 29 Sep 2011 12:12:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-5437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-5437:
--------------------------------------

    Issue & fix info:   (was: Patch Available)

Oops... The patch doesn't actually load the tables. Looking at the log in generated/toursdb/toursdb.out,
I see messages like this:

run 'loadCOUNTRIES.sql';
IJ ERROR: File not found
ij> run 'loadCITIES.sql';
IJ ERROR: File not found
ij> run 'loadAIRLINES.sql';
IJ ERROR: File not found
ij> run 'loadFLIGHTS1.sql';
IJ ERROR: File not found
ij> run 'loadFLIGHTS2.sql';
IJ ERROR: File not found
ij> run 'loadFLIGHTAVAILABILITY1.sql';
IJ ERROR: File not found
ij> run 'loadFLIGHTAVAILABILITY2.sql';
IJ ERROR: File not found

Probably because the working directory of the ij process isn't the directory in which the
sql files live.

While looking at the toursdb log, I also noticed an error that's also seen on a clean trunk,
where the toursdb.insertMaps program doesn't find the database. Filed DERBY-5438 to track
that problem.
                
> Load all toursdb tables in one invocation of ij
> -----------------------------------------------
>
>                 Key: DERBY-5437
>                 URL: https://issues.apache.org/jira/browse/DERBY-5437
>             Project: Derby
>          Issue Type: Improvement
>          Components: Demos/Scripts
>    Affects Versions: 10.9.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>         Attachments: d5437.diff
>
>
> The toursdb example database is built as part of "ant all". Currently, java/demo/toursdb/build.xml
invokes ij nine times, as well as a custom Java program (toursdb.insertMaps) once, to create
the database, and all of these run in separate Java processes. This means the database engine
is cold booted 10 times, which can take considerable time.
> There is already a script called loadTables.sql, which calls loadCOUNTRIES.sql, loadCITIES.sql,
loadAIRLINES.sql, loadFLIGHTS1.sql, loadFLIGHTS2.sql, loadFLIGHTAVAILABILITY1.sql and loadFLIGHTAVAILABILITY2.sql.
I propose that we use that script instead of invoking each of the sub-scripts separately.
This would reduce the number of times the database engine would have to be booted from 10
to 4 per full build.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message