Date: 10/05/00
- Next message: Theodore Hope: "[phplib] pages get cached in phplib!?!?"
- Previous message: Jeroen Laarhoven: "Re: [phplib]duplitcated Session ID?"
- In reply to: fabrizio.ermini <email protected>: "Re: [phplib] PHPLIB and oracle binding for >2000 characters"
- Next in thread: Chris Johnson: "RE: [phplib] PHPLIB and oracle binding for >2000 characters"
- Reply: Chris Johnson: "RE: [phplib] PHPLIB and oracle binding for >2000 characters"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Thanks!
My problem is at the application level. And, if I understand CT_split_SQL from a brief
look at it, I don't want to split data that belongs in one row up into multiple rows. The
Oracle column field is a CLOB and able to hold 4 GB, not just 4000 characters. It's just
that Oracle apparently requires one to input stings of more than 4000 characters in what
seems to me to be a rather obtuse manner, since I have never used "bind" variables.
The solution is quite possibly very simple. But from past experience with such things, I
know that I can easily take a wrong turn at some early point and end up making things very
complex long before I discover the simple solution ;-) Thus pointers to the right paths
to take will be much appreciated.
Cheers!
Mike Green
fabrizio.ermini <email protected> wrote:
> I'm not sure if your problem is related to session management or is
> application level. In the first case, I think that CT_split_SQL could
> be the answer to this problems (I use that in Postgres, where there
> is an analog problem cause tuples are limited in size, and works
> perfectly). If it's application level, you're on your own but I think
> CT_split could still be an useful source to browse at in search for
> possible solutions (i.e. splitting long strings of data in more
> records).
>
> > I have a similar problem.
> >
> > I installed a PHPLib-based system that had worked with MySQL, made the expected
> > necessary changes to date formats, and thought things were working well -- until
> > someone tried to insert a document with more than 4000 characters. [Not 2000. at
> > least I have something to be thankful for ;-)]
> >
> > The DBA tells me the Oracle error message that resulted comes with the solution "Use
> > a string literal of at most 4000 characters. Longer values may only be entered
> > using bind variables."
> >
> > I see that the PHP library has functions which are apparently for this (e.g.
> > OCIBindByName). But if I have to start from scratch to try to modify db_oci8.inc,
> > or whatever routine is appropriate, I may not get a working solution very soon. The
> > whole concept of a bind variable is a new one for me.
> >
> > I will much appreciate whatever tidbits on solutions to this that anyone can throw
> > my way!
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: phplib-unsubscribe <email protected>
For additional commands, e-mail: phplib-help <email protected>
- Next message: Theodore Hope: "[phplib] pages get cached in phplib!?!?"
- Previous message: Jeroen Laarhoven: "Re: [phplib]duplitcated Session ID?"
- In reply to: fabrizio.ermini <email protected>: "Re: [phplib] PHPLIB and oracle binding for >2000 characters"
- Next in thread: Chris Johnson: "RE: [phplib] PHPLIB and oracle binding for >2000 characters"
- Reply: Chris Johnson: "RE: [phplib] PHPLIB and oracle binding for >2000 characters"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

