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.

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

Test schema #1

Closed
aiida-bot opened this issue Oct 9, 2012 · 8 comments
Closed

Test schema #1

aiida-bot opened this issue Oct 9, 2012 · 8 comments
Labels
priority/critical-blocking must be resolved before next release type/task

Comments

@aiida-bot
Copy link

Originally reported by: AiiDA Team (Bitbucket: aiida_team, GitHub: Unknown)


Create a test script for operating with entities using ORM.


@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):


Check Issue #2 before playing around, so that it is easier to apply changes to our local DBs.

@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):


I setup a wiki page with some important schema changes to discuss. Please refer also to that.

@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):


Things to change, after discussion on skype on Tue Nov 13, 2012:

  • in DataClass: convert time to ctime (creation time, auto_now_add=True) and mtime (modification time, auto_now=True)
  • AttrTxtVal and similar tables (AttrNumVal, ...): do not depend on m.Model but on a abstract class; add both kind of times; add the user
  • AttrTxt and similar: instead, probably here the user is not really needed
  • title field: remove it from the BaseClass; put in each table that needs it, possibly with a different name, and a suitable 'unique' requirement, where needed. Examples: in Element, title should become symbol; in Calc and Struc, we don't really need titles; in AttrNum etc., it must be unique and can be called name instead of title
  • data field: experiment if there is a django json field that works (also with south). Otherwise, at least provide a suitable default string that gets parsed by json instead of raising an exception (e.g. "null" instead of "")
  • To test: OneToOne fields to move things in other tables, where needed

@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):


Also: change the name of fields to more descriptive, possibly longer ones

Some ideas:

  • struc->structure
  • calc->calculation, or job
  • incalc->incalculation
  • inppot->inpotential
  • ...

@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):


Moreover: remove the detail field from the structure (it will be stored in the file aida-storage/repository/structure/uuid/structure.json)

@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):


Old issue, now schema is completely different

@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):


fix issue #1 & #6, start working on dry-run.

@aiida-bot
Copy link
Author

Original comment by Spyros Zoupanos (Bitbucket: szoup, GitHub: szoupanos):


fix issue #1 & #6, start working on dry-run.

@aiida-bot aiida-bot added priority/critical-blocking must be resolved before next release type/task 0.4.0 labels Dec 23, 2016
waychal added a commit that referenced this issue Mar 3, 2017
Fixes the schema adding ordering and replacing "columns" by "fields"
DropD pushed a commit that referenced this issue Mar 15, 2017
giovannipizzi pushed a commit that referenced this issue Mar 15, 2017
API changes to log collection and entries
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/critical-blocking must be resolved before next release type/task
Projects
None yet
Development

No branches or pull requests

1 participant