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

IDBS-Spring20-Fudan/assignment3/readme/ #93

Open
utterances-bot opened this issue Apr 18, 2020 · 6 comments
Open

IDBS-Spring20-Fudan/assignment3/readme/ #93

utterances-bot opened this issue Apr 18, 2020 · 6 comments

Comments

@utterances-bot
Copy link

Instruction - IDBS-Spring20-Fudan

Course website for introduction to database systems at Fudan University

https://zfhu.ac.cn/IDBS-Spring20-Fudan/assignment3/readme/

Copy link

Whether it means that we can add more properties to book/student such as a bookid to identify each book as long as we meet all the requirements.
And whether the administrator's and students' accounts means that we should use some codes to create the accounts and give them some permissions or just use common strategies to simulate them (maybe parameters of a func ) without creating them actually.

Copy link

I think I solve the second problem I have asked before, but I want to make sure something

Who "query the borrow history of a student account" and
"query the books a student has borrowed and not returned yet"(also,check deadline, extend deadline)?
A student query his/her own or the administrator?

(Of course, these two situations are similar,I just want to make sure)

@ichn-hu
Copy link
Collaborator

ichn-hu commented Apr 20, 2020

Yes you can add mote properties. You are actually not restricted to do any thing. The requirements are kind of loose, you could make any reasonable modification and handle the vagueness in the requirements by your own design choices, just make sure you document and explain well in the report, and please justify your design choice whenever possible.

As said, for your second commemt, which way do you think is more proper? (I think both the student and the administer should be able to query.)

Actually, the difference in characters of users is up to you to design, and you are free to make any design decisions as long as your design is sound and the requirements are met (as long as you could explain the requirements are met, meaning you could somehow argue about it)

Copy link
Contributor

riteme commented Apr 27, 2020

Should we write Go tests on a real MySQL database or just a mock database (e.g. go-sqlmock)? Is it better to include table creation procedure in Go sources?

In my view, actual database setup is supposed to be separated from the library system, and the system is merely responsible for the specification of tables it relies on.

@ichn-hu
Copy link
Collaborator

ichn-hu commented Apr 27, 2020

I would suggest test it on actual database, and try to import some actual data in to the database.

I wouldn't say better, but it is okay.

The database is indeed part of the system, and you should make sure it works.

@Tan-YiFan
Copy link
Contributor

If I've implemented a simple command line interface, should I write tests on back-end (using test functions) or on front-end (e.g. using .sh scripts), or both?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants