[
https://issues.apache.org/jira/browse/DERBY-6937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036038#comment-16036038
]
Bryan Pendleton commented on DERBY-6937:
----------------------------------------
Great progress!
What was your "quick hack" for the NULL problem in the data? Was it:
1) You imported the data literally as-is, then ran a SQL UPDATE statement to
change "NULL" to a proper NULL value afterwards?
2) Or, you ran a Perl command or other tool over the data ahead-of-time to
replace "NULL" with an empty string prior to the import?
Either way seems fine to me, I was just wondering since I will try to reproduce
your findings.
I agree with you, the var-args problem that we encountered in DERBY-4555 was
rather fundamental and hard to avoid.
If it's easy enough to work around this NULL placeholder in the input dataset,
perhaps we can just disregard this minor inconvenience once we've documented
our approach, since our primary goal is to study the query optimizer, not to
work on the import/export tools?
> Load the IMDB data set in Derby, obtain and adapt Join order Benchmark
> queries for use in derby
> ------------------------------------------------------------------------------------------------
>
> Key: DERBY-6937
> URL: https://issues.apache.org/jira/browse/DERBY-6937
> Project: Derby
> Issue Type: Sub-task
> Components: SQL
> Reporter: Harshvardhan Gupta
> Assignee: Harshvardhan Gupta
> Priority: Minor
> Attachments: schema_derby.sql
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)