Ciao world_domination_kites,

On 9/20/06, world_domination_kites <[EMAIL PROTECTED]> wrote:
> I recon what's required is a special cursor encapsulates all that CLOB
> foolishness such that calling code can pretend it's a big text field.
> That way 'TextField' could map to CLOB, and nobody would have to know
> how unfortunate that was. By protection from variation, it would be
> tragic if anything outside backends.oracle had to do anything to
> accomodate CLOBs.
>
> db.backend.oracle.base.FormatStylePlaceholderCursor subclasses the
> cx_Oracle cursor. It already overloadeds the execute and executemany
> methods. Can you confirm that there would not be any calls to any other
> cursors?
>
> What if FormatStylePlaseholderCursor.execute<many>()
>  1. passed CLOBby SQL to the parent cursor as normal
>  2. inspected the columns
>  3 wrapped each CLOB colum in some sort of _read_CLOB_into_string()
> during the fetch.
>
> hey presto, it's as though CLOB columns hold big strings.

You can't do "LIKE" statements against a CLOB,
so you should also emulate the it as in:
http://www.developerdotstar.com/community/node/68

Ciao,
(c)

-- 
Carlo C8E Miron, ICQ #26429731
-- 
Disclaimer:
If I receive a message from you, you are agreeing that:
1. I am by definition, "the intended recipient".
2. All information in the email is mine to do with as I see fit and
 make such financial profit, political mileage, or good joke as it
 lends itself to. In particular, I may quote it on USENET or the WWW.
3. I may take the contents as representing the views of your company.
4. This overrides any disclaimer or statement of confidentiality that
 may be included on your message.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---

Reply via email to