home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.vms
- Path: sparky!uunet!cis.ohio-state.edu!magnus.acs.ohio-state.edu!ungyi@magnus.acs.ohio-state.edu
- From: Ung-Ho Yi <ungyi@magnus.acs.ohio-state.edu>
- Subject: cdd, c, and rdb 4.1
- Message-ID: <9212231344.AA20322@top.magnus.acs.ohio-state.edu>
- Sender: daemon@magnus.acs.ohio-state.edu
- Organization: The Ohio State University
- Date: Wed, 23 Dec 1992 13:44:37 GMT
- X-Mailer: ELM [version 2.3 PL11]
- Lines: 28
-
- thank you to people who have responded to my c and cdd question.
-
- some one asked what the DEC said about my problem.
- i only spoke with one technical support person, and he said i
- should create another record for C language, which is the same advice
- i got from most of you.
-
- I would also like to respond to the rdb v4.1 because we just went
- through with much difficulty.
- there were two problems we ran into.
-
- first was segmented string. i am not sure about the exact problem,
- but here it goes. our application program first stores 3
- bytes as segmented string,
- then later on the program adds more data on to the segmented string.
- this has always worked with rdb v4.0, but on rdb v4.1 it corrupted
- our database. the DEC engineers had manually remove the bad pages.
-
- second problem was with selecting rows. i heard this has to do with the
- optimization of the rdb.... some how, when we select rows and
- sort by some order, the query becomes very slow, much much slower then
- when we were using rdb v4.0. so, we had to change some of our application
- programs again.
-
-
- that's all and good luck to people who are changing version on rdb.
-
- yi
-