Typing clob

On the client or server computer. LOCOPY FunctionThe LOCOPY function creates a copy of a smart large object. The first parameter specifies the BLOB or CLOB column to copy. The table name and column name parameters are optional:If you omit table name and column name, the LOCOPY function creates a smart large object with system-specified storage defaults and copies the data in the BLOB or CLOB column into it. It obtains the system-specific storage defaults from either the ONCONFIG file or the sbspace. For more information on system-specified storage defaults, see the INFORMIX-Universal Server Administrator's Guide.When you specify a table name and column name, the LOCOPY function uses the storage characteristics from the specified column name for the BLOB or CLOB value that it creates.The LOCOPY function returns a handle value (a pointer) to the new BLOB or CLOB value. This function does not actually store the new smart-large-object value into a column in the database. You must assign the BLOB or CLOB value to the appropriate column.The following ESQL/C code fragment copies the CLOB value in the resume column of the candidate table to the resume column of the interview table:/* Insert a new row in the interview table and get the * resulting SERIAL value (from sqlca.sqlerrd[1]) */EXEC SQL insert into interviews (intrv_num, intrv_time) values (0, '09:30');intrv_num = sqlca.sqlerrd[1];/* Update this interview row with the candidate number * and resume from the candidate table. Use LOCOPY to * create a copy of the CLOB value in the resume

Handle value share the CLOB or BLOB value across several columns. This storage arrangement reduces the amount of disk space that the CLOB or BLOB data takes. However, when several columns share the same smart-large-object value, the following conditions result:The chance of lock contention on a CLOB or BLOB column increases. If two columns share the same smart-large-object value, the data might be locked by either column that needs to access it. The CLOB or BLOB value can be updated from a number of pointsTo remove these constraints, you can create separate copies of the BLOB or CLOB data for each column that needs to access it. You can use the LOCOPY function to create a copy of an existing smart large object. You can also use the SQL functions LOTOFILE, FILETOCLOB, and FILETOBLOB to access smart-large-object values. For more information on these functions, see "Smart-Large-Object Functions". For more information on the BLOB and CLOB data types, see Chapter 2 of the Informix Guide to SQL: Syntax. Constant Expressions The following diagram shows the possible syntax for constant expressions. ElementPurposeRestrictionsSyntaxdatetime unitOne of the units that is used to specify an interval precision; that is, YEAR, MONTH, DAY, HOUR, MINUTE, SECOND, or FRACTION. If the unit is YEAR, the expression is a year-month interval; otherwise, the expression is a day-time interval.The datetime unit must be one of the keywords that is listed in the Purpose column. You can enter the keyword in uppercase or lowercase letters. You cannot put quotation marks

CLOB value to the appropriate column.GLSThe FILETOCLOB function performs any code-set conversion that might be required when it copies the file from the client or server computer to the database. The following INSERT statement uses the FILETOCLOB function to create a CLOB value from the value in the haven.rsm file:INSERT INTO candidate (cand_num, cand_lname, resume) VALUES (0, 'Haven', FILETOCLOB('haven.rsm', 'client'))In the preceding example, the FILETOCLOB function reads the haven.rsm file in the current directory on the client computer and returns a handle value to a CLOB value that contains the data in this file. Because the FILETOCLOB function does not specify a table and column name, this new CLOB value has the system-specified storage characteristics. The INSERT statement then assigns this CLOB value to the resume column in the candidate table. LOTOFILE FunctionThe LOTOFILE function copies a smart large object to an operating-system file. The first parameter specifies the BLOB or CLOB column to copy. The function determines the operating-system file to create from the following parameters:The pathname parameter identifies the directory path and name of the source file.The file destination parameter identifies the computer, client or server, on which this file resides:Set file destination to 'client' to identify the client computer as the location of the source file. The pathname can be either a full pathname or relative to the current directory.Set file destination to 'server' to identify the server computer as the location of the source file. The pathname must be a full pathname.By default, the LOTOFILE function

While migrating my application from DB2 to PostgreSQL.I want to migrate following functions in PostgreSQL.Functions in DB2: BLOB()/CLOB()Criteria:Size of character string targeted for cast is more than 1GB. CharacterString as argument to this function.How can I migrate this function into PostgreSQL with above mention criteria.--View this message in context: from the PostgreSQL - general mailing list archive at Nabble.com. Am 19.06.2013 08:05, schrieb sachin kotwal:While migrating my application from DB2 to PostgreSQL.I want to migrate following functions in PostgreSQL.Functions in DB2: BLOB()/CLOB() Criteria: Size of character string targeted for cast is more than 1GB. CharacterString as argument to this function.How can I migrate this function into PostgreSQL with above mention criteria. Hi, as i know each value is limited to 1GB. For larger content use module lo Thomas >as i know each value is limited to 1GB. For larger content use module lo> just want to know that like DB2 we can convert other data types intoCLOB/BLOB using function CLOB()/BLOB().Example:SELECT CLOB('testdata') FROM SYSIBM.SYSDUMMY1Same way i want to convert other data types into large objects Oid inPostgreSQL.Proposed SQL will like:select col1::oid from hoge;------OR------select to_oid('testdata');Can anyone tell me that how I can implement above function for conversion?--View this message in context: from the PostgreSQL - general mailing list archive at Nabble.com. On Fri, Jun 21, 2013 at 9:40 PM, sachin kotwal wrote:>>as i know each value is limited to 1GB. For larger content use module lo>> I just want to know that like DB2 we can convert other data types into> CLOB/BLOB