Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

allow overwriting of collectionTable #281

Open
tkrojer opened this issue Jan 16, 2020 · 2 comments
Open

allow overwriting of collectionTable #281

tkrojer opened this issue Jan 16, 2020 · 2 comments
Assignees
@tkrojer
Labels
enhancement Medium

Comments

@tkrojer
Copy link

tkrojer commented Jan 16, 2020

Usually, each auto-processing run is only parsed one time because an entry is created in the collectionTable, and it is ignored the next time if an entry exisits. This is necessary because XChem data collection visits usually last for months and this would result in redundant and consequently very slow parsing. However, there may be instances when one wants to read everything from scratch. Right now the solution is to either remove the entries from the collectionTable or to drop the entire table.
@tkrojer tkrojer self-assigned this Jan 16, 2020
@tkrojer
Copy link
Author

tkrojer commented Jan 16, 2020

Additionally, set DataProcessingAutoAssigned to True in mainTable, otherwise the results will be copied over, but will not be linked!
update mainTable set DataProcessingAutoAssigned='True' where DataProcessingAutoAssigned='False'

@tkrojer
Copy link
Author

tkrojer commented Jan 16, 2020

Last issue was solved in v1.4.5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tkrojer tkrojer

Labels
enhancement Medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tkrojer