RE:problemas con una select con un campo long
Para tu informacion:
-Only one LONG column is allowed per table.
-LONG columns cannot be indexed.
-LONG columns cannot appear in integrity constraints.
-LONG columns cannot be used in WHERE, GROUP BY, ORDER
BY, CONNECT BY clauses, or with the DISTINCT operator in
SELECT statements.
-LONG columns cannot be referenced by SQL functions (such as
SUBSTR or INSTR).
-LONG columns cannot be used in the SELECT list of a subquery
or queries combined by set operators (UNION, UNION ALL,
INTERSECT, or MINUS).
-LONG columns cannot be used in expressions.
-LONG columns cannot be referenced when creating a table with a
query (CREATE TABLE . . . AS SELECT . . .) or when inserting into
a table (or view) with a query (INSERT INTO . . . SELECT . . .).
-A variable or argument of a PL/SQL program unit cannot be
declared using the LONG datatype.
-Variables in database triggers cannot be declared using the
LONG or LONG RAW datatypes.
-References to :NEW and :OLD in database triggers cannot be
used with LONG or LONG RAW columns.
Ahora lo que comunmente se realiza cuando existe un campo log es tener dos tablas, por ejemplo:
tabla1 codigo, autor, anio, paginas, edicion
tabla2 codigo, texto(LONG)
entonces siempre trabajarias con la tabla1 porque alli tienes toda la informacion del texto que es de tipo LONG y la tabla2 unicamente la utilizas cuando ya necesitas mostrar el contenido de texto asociado con codigo en las dos tablas
Te sirve o no ? ...