Recently the company usual are power off. This morning it happent again, so that our team database server
is crushed. I am going to go on yesterday's testing. But it have to be suspending. Yesterday I found a bug,
which is a wrong title name. After corrected, today must test it.
This project was coded in PRO *C. The PROC *C was designed to write applications base on Oracle DBMS. In
the codes of programs, there are many a function that have written in so long, the partial reason is that
PRO *C. The SQL is embeded in C codes. Sometimes the variables used in SQL confused programmers. This variable
can satisfy the SQL as argurments, but the average C variable is not used in that way. However, those variables
can not be as parameters of a function. So, programmers must copy data into a PRO *C varialbe from a C variable,
having gotten a value passed into. Therefore, a great number of declaring PRO *C variables statements almost
are whereever.
To write an application in PRO *C is unhappy!
昨日の夜、私は病院へ行きました。祖母は病気をひくことがあります。
is crushed. I am going to go on yesterday's testing. But it have to be suspending. Yesterday I found a bug,
which is a wrong title name. After corrected, today must test it.
This project was coded in PRO *C. The PROC *C was designed to write applications base on Oracle DBMS. In
the codes of programs, there are many a function that have written in so long, the partial reason is that
PRO *C. The SQL is embeded in C codes. Sometimes the variables used in SQL confused programmers. This variable
can satisfy the SQL as argurments, but the average C variable is not used in that way. However, those variables
can not be as parameters of a function. So, programmers must copy data into a PRO *C varialbe from a C variable,
having gotten a value passed into. Therefore, a great number of declaring PRO *C variables statements almost
are whereever.
To write an application in PRO *C is unhappy!
昨日の夜、私は病院へ行きました。祖母は病気をひくことがあります。