home *** CD-ROM | disk | FTP | other *** search
-
-
-
-
- OVQP(ERROR) 3/30/79 OVQP(ERROR)
-
-
-
- NAME
- One Variable Query Processor error message summary
-
- SYNOPSIS
- Error numbers 4000 - 4499.
-
- DESCRIPTION
- These error messages can be generated at run time. The One
- Variable Query Processor actually references the data, pro-
- cessing the tree produced by the parser. Thus, these error
- messages are associated with type conflicts detected at run
- time.
-
- ERRORS
- 4100 ovqp query list overflowed
-
- This error is produced in the unlikely event that
- the internal form of your interaction requires more
- space in the one variable query processor than has
- been allocated for a query buffer. There is not
- much you can do except shorten your interaction or
- recompile OVQP with a larger query buffer.
-
- 4106 the interpreters stack overflowed -- query too long
- 4107 the buffer for ASCII and CONCAT commands overflowed
-
- More buffer overflows.
-
- 4108 cannot use arithmetic operators on two character
- fields
- 4109 cannot use numeric values with CONCAT operator
-
- You have tried to perform a numeric operation on
- character fields.
-
- 4110 floating point exception occurred.
-
- If you have floating point hardware instead of the
- floating point software interpreter, you will get
- this error upon a floating point exception (under-
- flow or overflow). Since the software interpreter
- ignores such exceptions, this error is only possible
- with floating point hardware.
-
- 4111 character value cannot be converted to numeric due
- to incorrect syntax.
-
- When using int1, int2, int4, float4, or float8 to
- convert a character to value to a numeric value, the
- character value must have the proper syntax. This
- error will occur if the character value contained
- non-numeric characters.
-
- 4112 ovqp query vector overflowed
-
- Similar to error 4100.
-
- 4113 compiler text space ran out
- 4114 compiler ran out of registers
-
- These errors refer to an experimental version of the
- system that is not currently released.
-
- 4199 you must convert your 6.0 secondary index before
- running this query!
-
- The internal format of secondary indices was changed
- between versions 6.0 and 6.1 of INGRES. Before de-
- ciding to use a secondary index OVQP checks that it
- is not a 6.0 index. The solution is to destroy the
- secondary index and recreate it.
-
-
-