-
Notifications
You must be signed in to change notification settings - Fork 0
Meetings
- Participants: Radu, Claudiu
- Place/time: EG106a, 7pm
- Purpose: Kick-off meeting
- Know the team
- Present objectives
- Technical information on the project
- Tools of the trade
- Weekly meetings plan and tasks
Currently MySQL support is there. We need Postgresql support with simple and parameter queries. If time allows, use simple queries in MySQL.
Show the main JDBC classes, what has already been done for MySQL and what needs to be done for PGSQL.
Tools to use: SpiderMonkey (libmozjs), C/JavaScript, GCC toolchain Tools: Use GitHub repository Tools: For the time being use direct e-mails
Weekly meeting: Wednesday, 8pm Next meeting: Wednesday, March 26, 2014, 8pm, room EG106a
Claudiu: Create plan (include 3-4 milestones) for work.
Claudiu: For the short term:
- browse source code and documentation
- setup work environment
- compile sources and toy around with the project
- get to know JDBC
- get to know JavaScript
- get to know SpiderMonkey
Claudiu: Setup architecture until next meeting (Wednesday, March 26, 2014, 8pm)
Claudiu: Setup user scenarios
- Participants: Radu, Claudiu, Razvan
- Place/time: EG106a, 8pm
- Purpose: Report for the last 2 weeks
- Project status
There were discussion about the plan for work proposed by Claudiu.
Also Claudiu discovered that the newest release of Mozilla's JavaScript engine (SpiderMonkey 24) doesn't support the C API anymore so we talked about this issue and how it will affect the project.
Weekly meeting: Wednesday, 8pm Next meeting: Wednesday, April 9, 2014, 8pm room EG106a
Claudiu:
- Talk with SpiderMokey's developers about the changes which will be made on SpiderMonkey 31 and if there are any chances to revert the C API for JSAPI in the new release or in the future.
- Use GNU Autotools project in order to make libjssql more portable
- Implement a module skeleton for the PostgreSQL driver
- Implement connection functionality
After Claudiu talked with some developers from the SpiderMonkey project [1] we decided to continue the development using the SpiderMonkey 17 API. This decision was made because of several reasons:
- the current functionality is written in C and SpiderMonkey 17 is the latest version which has support for C
- porting the project to C++ will take too long and Claudiu doesn't have enough time to finish his bachelor project
- SpiderMonkey's developers don't expect for the C++ API to be stable very soon
In conclusion, libjssql library will be compatible only with the SpiderMonkey 17 release. In the near future we plan to port the whole library in C++.
[1] - link with discussion about the SpiderMonkey 31 release
- Participants: Radu, Claudiu, Razvan
- Place/time: EG106a, 8pm
- Purpose: Report for the last 2 weeks
- Project status
Claudiu had some issues using the GNU Autotools and there were some discussions about these and about how he should organize his work.
Also we discussed about how to make the code more generic in order to reuse some parts implemented on MySQL driver.
Weekly meeting: Wednesday, 8pm Next meeting: Wednesday, April 23, 2014, 7pm room EG106a
Claudiu:
- Finish implementing the Autotools functionality.
- Implement simple queries
- Participants: Claudiu, Razvan
- Place/time: EG106a, 7pm
- Purpose: Report for the last 2 weeks
- Project status
There were discussions about how the JavaScript API exposed by libjssql library will look.
Also we discussed about the unit tests. They should be small tests written in JavaScript which will test simple functionalities like connection , simple query execution or parameter query execution. Each test will be written immediately after the tested functionality is implemented.
Weekly meeting: Wednesday, 8pm Next meeting: Wednesday, May 7, 2014, 8pm room EG106a
Claudiu:
- Finish implementing simple queries
- Write project status on wiki
- Implement execution functionality for simple and prepared queries
- Implement parameter queries