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

Add non-interactive options for interactive tools like dj.new and dj.createSchema #69

Closed
eywalker opened this issue Feb 7, 2017 · 2 comments · Fixed by #327
Closed
Assignees
Labels
enhancement tomerge awaiting merge before close
Milestone

Comments

@eywalker
Copy link
Contributor

eywalker commented Feb 7, 2017

Interactive tools like dj.new and dj.createSchema offers convenient ways of creating new schemas/tables. However, there are no non-interactive equivalent to these tools such that there is no way to create schema/table (easily) from a non-attended script. It would perhaps be nice to either offer non-interactive modes to these functions or come up with non-interactive alternatives all together.

@eywalker eywalker self-assigned this Feb 7, 2017
@dimitri-yatsenko
Copy link
Member

This may just take the form of arguments passed into these functions. Without input, they become interactive.

@eywalker
Copy link
Contributor Author

eywalker commented Feb 8, 2017

This would have been far cleaner to implement if Matlab function had a (clean) way to implement default values. I'm thinking that createSchema can expect two arguments - database name and package path. Just like how I modified the current version, I would like to be able to pass in just the name of the package to trigger GUI to choose a folder to create the package in (this is convenient when triggering createSchema from dj.new. I'm not sure what would be the cleanest way to do this yet.

dj.new can expect to take in two arguments as well - name of table (schema.table) and the type of the table. I'm thinking that if the type of the table is not specified then it will automatically use Manual table. If name of table was passed into dj.new but the schema doesn't exist, then we should just throw an error rather than triggering dj.createSchema.

@dimitri-yatsenko dimitri-yatsenko added this to the Release 3.1 milestone Apr 17, 2017
guzman-raphael added a commit to guzman-raphael/datajoint-matlab that referenced this issue Dec 8, 2020
guzman-raphael added a commit that referenced this issue Dec 8, 2020
Update release history and include fix for #69 and #311
@guzman-raphael guzman-raphael added the tomerge awaiting merge before close label Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement tomerge awaiting merge before close
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants