JAL: add `'s`

2018-03-19T19:41:14Z

add <var>'s

← Older revision		Revision as of 19:41, 19 March 2018
Line 1:		Line 1:
	{{Template:M204.2452 skeleton}}		{{Template:M204.2452 skeleton}}

	<P>A Model 204 field is indexed, but this index cannot be used in SQL applications, because the SQL datatype of a column mapped to the field does not match the field datatype.</P>		<P>
	<P>This message might be produced during SQL query compilation in the following cases:</P>		A Model 204 field is indexed, but this index cannot be used in SQL applications, because the SQL datatype of a column mapped to the field does not match the field datatype.</P>
	<ul><LI>Field is ~~ORDERED CHARACTER, but SQL column type is not CHARACTER.~~<~~/LI><LI~~>~~Field is~~ ORDERED ~~NUMERIC, but SQL column type is~~ CHARACTER.</LI>~~<LI>Field is KEY STRING~~, but SQL column type is not ~~CHARACTER.~~<~~/LI~~>~~<LI>Field is KEY or HASH, its datatype is BINARY or FLOAT, but SQL column type is~~ CHARACTER.</LI>~~<LI>Field is KEY or HASH, its datatype is STRING, but SQL column type is not CHARACTER~~.</LI~~></ul>~~		<P>
	~~<p><b>Response:</b> Notify the System Manager.</p>~~		This message might be produced during SQL query compilation in the following cases:</P>
	~~<p><b>System manager response:</b> If possible, either redefine the field, or alter or recreate the table to change the column datatype, so that there is no datatype mismatch.</p~~>		<ul>
			<LI>Field is <var>ORDERED CHARACTER</var>, but SQL column type is not <var>CHARACTER</var>.</LI>

			<LI>Field is <var>ORDERED NUMERIC</var>, but SQL column type is <var>CHARACTER</var>.</LI>

			<LI>Field is <var>KEY STRING</var>, but SQL column type is not <var>CHARACTER</var>.</LI>

			<LI>Field is <var>KEY</var> or <var>HASH</var>, its datatype is <var>BINARY</var> or <var>FLOAT</var>, but SQL column type is <var>CHARACTER</var>.</LI>

			<LI>Field is <var>KEY</var> or <var>HASH</var>, its datatype is <var>STRING</var>, but SQL column type is not <var>CHARACTER</var>.</LI>
			</ul>
			<p>
			<b>Response:</b> Notify the System Manager.</p>
			<p>
			<b>System manager response:</b> If possible, redefine the field, or alter or recreate the table to change the column datatype, so that there is no datatype mismatch.
			</p>
	{{Template:M204.2452 footer}}		{{Template:M204.2452 footer}}
	<!-- skeleton as it was in pdf/INDEX FOR indextype FIELD fieldname CANNOT BE USED IN SQL QUERY PROCESSING/-->		<!-- skeleton as it was in pdf/INDEX FOR indextype FIELD fieldname CANNOT BE USED IN SQL QUERY PROCESSING/-->

DmeWiccan: Automatically generated page update

2018-03-14T03:46:18Z

Automatically generated page update

New page

{{Template:M204.2452 skeleton}}

A Model 204 field is indexed, but this index cannot be used in SQL applications, because the SQL datatype of a column mapped to the field does not match the field datatype.
This message might be produced during SQL query compilation in the following cases:
<ul><LI>Field is ORDERED CHARACTER, but SQL column type is not CHARACTER.</LI><LI>Field is ORDERED NUMERIC, but SQL column type is CHARACTER.</LI><LI>Field is KEY STRING, but SQL column type is not CHARACTER.</LI><LI>Field is KEY or HASH, its datatype is BINARY or FLOAT, but SQL column type is CHARACTER.</LI><LI>Field is KEY or HASH, its datatype is STRING, but SQL column type is not CHARACTER.</LI></ul>
Response: Notify the System Manager.
System manager response: If possible, either redefine the field, or alter or recreate the table to change the column datatype, so that there is no datatype mismatch.

{{Template:M204.2452 footer}}

M204.2452 - Revision history

JAL: add 's

DmeWiccan: Automatically generated page update

JAL: add `'s`