Create Index in the output database

[katyhuff]

Suggestion from Yarden ( @yarden-livnat ) :

One of the last steps of database creation should be indexing (CREATE_INDEX ? )
Since it takes some time (how much?), it's likely that we will want a flag that turns off this feature for parametric simulation sets (because creating the index at the end of each simulation is fine, but is probably better to do just once at the end of the parametric series).

We should do this probably by adding a line to the create-table function for the sqlite backend that adds the name of that table to the list of tables to index.

Then, at the beginning of the close-table function in that sqlite backend, create an index based on that list.

[scopatz]

Moved to 0.4

[scopatz]

Moved to v0.5, probably should be post-1.0

[rwcarlsen]

My post-processing tools do a fair amount of this. FWIW.

On Mon, Feb 3, 2014 at 6:00 AM, Anthony Scopatz notifications@github.comwrote:

Moved to v0.5, probably should be post-1.0

Reply to this email directly or view it on GitHubhttps://github.com//issues/603#issuecomment-33946832
.

[scopatz]

I agree that this is mostly not relevant to the core.

[rwcarlsen]

Now that I have more experience, we can't really guess what indices any user will want. There are divers permutations of indices and we certainly can't/shouldn't create them all. I don't think the core should try to guess. Post processing tools will create different indices depending on what we are post-processing for - e.g. create indices specific to cyclist, etc. I'd be fine with closing this issue.

[scopatz]

Agreed for now.

[yarden-livnat]

Indeed.
I don't think the core should create any indices, certainly not while it is still dumping data.

On Mar 7, 2014, at 3:06 PM, Robert Carlsen notifications@github.com wrote:

Now that I have more experience, we can't really guess what indices any user will want. There are divers permutations of indices and we certainly can't/shouldn't create them all. I don't think the core should try to guess. Post processing tools will create different indices depending on what we are post-processing for - e.g. create indices specific to cyclist, etc. I'd be fine with closing this issue.

—
Reply to this email directly or view it on GitHub.

[scopatz]

Not going to happen by 1.0

[rwcarlsen]

FWIW my post-processing tool in cyan does this, but it won't be an
official part of the cyclus 1.0 release.

On Sat, May 17, 2014 at 11:45 AM, Anthony Scopatz
notifications@github.comwrote:

Not going to happen by 1.0

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/603#issuecomment-43414262
.

[scopatz]

Moved to 1.2

[scopatz]

Moved to v1.3

[gidden]

@rwcarlsen / @yarden-livnat, can you give an update on this issue?

[rwcarlsen]

I think that this is the responsibility of cymetric, cyclist, and other
data analysis tools. I would vote for moving this issue into cymetric and
closing it here.

On Fri, Apr 24, 2015 at 10:38 AM, Matthew Gidden notifications@github.com
wrote:

@rwcarlsen https://github.com/rwcarlsen / @yarden-livnat
https://github.com/yarden-livnat, can you give an update on this issue?

—
Reply to this email directly or view it on GitHub
#603 (comment).

[gidden]

opening cyclus/cymetric#54