英语翻译This was one area where we had just enough experience to

英语翻译
This was one area where we had just enough experience to be dangerous.We knew it could be done and this was one potential hot spot.In evaluating various database packages,we looked at the licensing terms and the availability of support for embedded and web applications.It seemed as though many of the databases available for Linux took care of the last two requirements.The licensing aspect was more varied in that several of the better-known packages provided for a single user or non-commercial use at no fee.Since we would be installing this on many systems and for commercial purposes,licensing was an issue we didn't want to overlook.When we pursued it,we found some of the license fees were higher than the going rate for MS Access.That alone eliminated some of the choices.We eventually settled on using PostgreSQL.Besides the very liberal copyright,we were strongly influenced by the availability of high-quality documentation.Having the opportunity to review the manuals before even committing to downloading the code was enough to reassure us this was a good path to follow.
Once the database was chosen,we had to get down to the details of implementation.The first part was to define the schema.Having had some experience with SQL previously,I found that psql was easily adapted.Knowing that the schema was likely to change as the project evolved,I wrote a few scripts to define all the tables and fill in default values.This took care of setting up the database.The next step was to define the interface to the control program.On the same premise that the database schema would change,I set up the interface as a separate module with subroutines to read selected data into working buffers.With the exception of the log table,all of the tables were read only for this function.Thus,there is a subroutine to read a selected record from each of the tables.The only other exception to this approach is that when the system first came up,a way was needed to determine just how many doors were implemented.This merely took a set of subroutines that would open the table,return the next entry in the table on each call and then close the table.This allowed the program to scan all possible entries to set up the communications links and other structures.All the functionality I needed was provided by the lilbpq library included with the distribution.It turned out to be easier than I had first expected.
有一些是计算机术语
只要流畅就行了,想要分就来拿吧
我写错了,是80分,我说到做到.

这是一个我们刚刚具备足够经验以涉险的区域.我们认为它是一个可行的潜在热点.在分析了不同的数据包之后,我们将重点放在了许可证条款和对于嵌入式系统的支持以及网络应用的有效性上.看起来好像Linux在软件包的后两点上下了功夫.对于许可证方面,在那些出名的软件包里好像只有几个对于个人用户或是非商业用途是免费的.由于我们的软件可能要装在很多系统上用于商业目的,所以我们不会忽视许可证这一块.当我们对其（许可证收费?）进行追踪的时候,我们发现有些许可证费比MS Access的现行利率都要高.单这样就排除了一些选择.最后当我们把目光锁定在PostgreSQL上,除了开放的版权,我们还被它的高质量的文件所震撼.仅仅是在下载代码之前再次回顾下其手册就打消了我们跟随这条路的所有疑虑.
数据库一旦选定后,我们就必须要彻底的执行了.第一部分是定义计划,我发现在拥有前面做SQL的经验之后,PSQL(PostgreSQL)就很容易上手了.由于随着项目的发展,计划也有可能变化,所以我写了一些脚本来定义所有的表和填入一些缺省值.这样数据库就很好的建立起来了.下一步是定义控制计划的界面,同样由于数据库计划可能变化,我将控制计划设置为一个拥有可以在工作缓冲区中读取选定数据的子程序的独立的模块.在此功能中,除了日志文件,其他表都被设置成只读的.因此就有了一个从各个表格中读取选定纪录的子程序.这种方式只有一个例外,那就是——当系统初次运行的时候需要一个方法来决定采用多少个通道.这仅仅是一组子程序在每次命令中打开表,返回表中下一个的入口然后关闭表.这样程序就能检验所有的入口以及建立与其他结构的链接.所需要的功能全部都是由发行物中所包含的lilbpq库提供,这比我初步预计的要简单
.不知道为什么,刚刚的头没了..重打了遍,郁闷