home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases.oracle
- Path: sparky!uunet!charon.amdahl.com!amdahl!rtech!pacbell.com!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!hermes.chpc.utexas.edu!news.utdallas.edu!corpgate!crchh327!n8ppd001!jhs
- From: jhs@n8ppd001.nt.com (jhs)
- Subject: Re: Pro*c and SVR4
- Message-ID: <C1GoBv.5v3@news.rich.bnr.ca>
- Sender: jhs@n8ppd001 (jhs)
- Date: Tue, 26 Jan 1993 12:35:54 GMT
- Lines: 23
- Reply-To: cmjxs04@nt.com (jhs)
- References: <1993Jan25.221224.651@cbnewsj.cb.att.com>
- Nntp-Posting-Host: 131.253.248.61
- Organization: Northern Telecom, RTP NC
- Keywords: varchar warnings
-
-
- |>
- |>
- |>We were looking for a precompiler option but there doesn't seem to be one
- |>that would resolve this problem. Does anyone out there have any simplier
- |>ideas on how to solve this?
- |>
- |>We are using oracle version V6.0.33.1.2 and oracle precompiler
- |>version 1.3.18.1.2
- |>
-
- Unfortunately there is no option to fix the unsigned char problem.
-
- We are using the version 1.4 and 1.5 precompilers. They correct
- several other deficiencies, but they still have the same type 'error'.
- The problem is even worse when you try to embed SQL in C++. The type
- mismatch with standard string functions cause a lot of problems.
-
- Some people run a filter on the output of pcc/proc before running cc
- to clean up the varchar declarations.
-
- john
-
-