Our team is beginning to hit the panic button. We are still unable to make SQL 7.0 functional. Leslie spoke with Professor Stotts about the problem and he referred her to William Jiang, who ended up not being able to help with the situation. Jiang explained that he had set up SQL 6.5 and that his best advice for us was to find a good book about SQL. Unfortunately, we had already taken that route and none of the books we now own cover the necessary material.Respond to Leslie (producer)
In our most recent meeting we did develop some alternatives. Randy consulted a former co-worker of his who also has expereince in this line of work. He will be informing us of what he found out at our team meeting tomorrow. Brett contacted some of his father's emplyees and arranged a meeting which will occur this coming Thursday. We were all in agreement that SQL 7.0 is definitely the solutions, given the English Query feature. In addition to our SQL problems, we learned that to implement English Query, and English Query kernel must be written to go between the request and the database. This kernel defines the relationships among the data in our database. This kernel is speculated to be quite complex. More information about the writing of the kernel should be available tomorrow. Mike and Patrick have the responsibility of studying example kernels' code and determining what the next steps to be taken are. However, time is running very short and if our server is still not functional by this coming Friday, we are going to take an alternate course.
Our worst-case-scenario plan is to build the project strictly in Perl, utilizing the UNIX database. We are aware that a database can be written to and searched in UNIX, using the Perl dbmopen and dbmclose commands. Reverting to this plan means that we also have to write code to analyze the query entered by the user. This code segment would have to be basic, but would serve its purpose given the scope of our project.
In order to meet our deadline and make much needed progress, we have decided to increase our number of weekly team meetings. Our meetings will now be set on a per meeting basis, meaning that the next meeting time will be set during the present meeting.