This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:indexing:text:clob [2011/03/31 14:42] 127.0.0.1 external edit |
admin:indexing:text:clob [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 10: | Line 10: | ||
| [[admin:indexing:text:retrieve|External Files]] | | [[admin:indexing:text:retrieve|External Files]] | | ||
| [[admin:indexing:text:proximity|Proximity Searches]] | | [[admin:indexing:text:proximity|Proximity Searches]] | | ||
| + | [[admin:indexing:text:advanced|Advanced Searches]] | | ||
| [[admin:indexing:text:results|Displaying Results]] | | [[admin:indexing:text:results|Displaying Results]] | | ||
| [[admin:indexing:text:relevancy|Relevancy]] | [[admin:indexing:text:relevancy|Relevancy]] | ||
| Line 25: | Line 26: | ||
| |\\ \\ \\ **CHARACTER**\\ \\ \\ \\ |Space-padded data up to 4,095 bytes.| | |\\ \\ \\ **CHARACTER**\\ \\ \\ \\ |Space-padded data up to 4,095 bytes.| | ||
| |\\ \\ \\ **STRING** \\ \\ \\ \\ |Null-terminated data up to 64MB. If indexed with Omnidex, the extracted text from this column may be up to 16MB.| | |\\ \\ \\ **STRING** \\ \\ \\ \\ |Null-terminated data up to 64MB. If indexed with Omnidex, the extracted text from this column may be up to 16MB.| | ||
| - | |\\ \\ \\ **VARCHAR** \\ \\ \\ \\ |Non-terminated and non-padded data up to 4,095 bytes. This datatype may contain embedded null characters since it is not null-terminated; however, it should not be used to store binary data. Use of this datatype requires use of data lengths variables since no terminator is used to indicate the end of the text. This datatype is therefore not appropriate for fixed length Flatfiles since the data length cannot be stored. Flatfiles should use CHARACTER or STRING datatypes.| | + | |\\ \\ \\ **VARCHAR** \\ \\ \\ \\ |Non-terminated and non-padded data up to 4,095 bytes. This datatype may contain embedded null characters since it is not null-terminated; however, it should not be used to store binary data. When using API's to access this datatype, data lengths variables are required since no terminator is used to indicate the end of the text. This datatype is also not appropriate for fixed length raw data files since the data length cannot be stored in raw data files. Raw data files should use CHARACTER or STRING datatypes.| |
| - | |\\ \\ \\ **CLOB** \\ \\ \\ \\ |Non-terminated and non-padded data up to 64MB. If indexed with Omnidex, the extracted text from this column may be up to 16MB. This datatype may contain embedded null characters since it is not null-terminated; however, it should not be used to store binary data. Use of this datatype requires use of data lengths variables since no terminator is used to indicate the end of the text. This datatype is therefore not appropriate for fixed length Flatfiles since the data length cannot be stored. Flatfiles should use CHARACTER or STRING datatypes.\\ \\ The handling of CLOB data may be more expensive than the handling of CHARACTER, STRING and VARCHAR data. It is better to use those datatypes if their size limitations will not be exceeded.| | + | |\\ \\ \\ **CLOB** \\ \\ \\ \\ |Non-terminated and non-padded data up to 64MB. If indexed with Omnidex, the extracted text from this column may be up to 16MB. This datatype may contain embedded null characters since it is not null-terminated; however, it should not be used to store binary data. When using API's to access this datatype, data lengths variables are required since no terminator is used to indicate the end of the text. This datatype is also not appropriate for fixed length raw data files since the data length cannot be stored in raw data files. Raw data files should use CHARACTER or STRING datatypes.\\ \\ The handling of CLOB data may be more expensive than the handling of CHARACTER, STRING and VARCHAR data. It is better to use those datatypes if their size limitations will not be exceeded.| |
| \\ | \\ | ||
| ---- | ---- | ||