Thanks. I added ora_ph_type as a way to
a) experiment with changing the bind type for strings, and b) provide a backdoor for people who might be affected if I did change the default (I'd add a way to set it via an env var). It needs to be shown to be working (and documented :) before I can think seriously about changing the default. Have a play with t/ph_type.t in the source tree - set $muted to 0 at the top. Tim. On Tue, Oct 16, 2001 at 02:56:20PM -0500, Michael A Chase wrote: > The main impetus that I can see for using ora_ph_type is to restore the old > Oraperl behavior for strings. Personally, I feel if someone really wants to > put NULs in a character field, they should have to do the extra work, not > those who want spaces at the end of their fields. For that reason, I > suggest consideration for changing the default ora_type for string values > back to 5. > > I have not forgotten that I offered to document ora_ph_type a couple months > ago. Unfortunately, when I did some tests, the results were not what I > expected. I then got busy at work and did not find the time to track down > the problem (if any). I plan to take another crack at it in the next week > or so. > -- > Mac :}) > ** I normally forward private questions to the appropriate mail list. ** > Give a hobbit a fish and he eats fish for a day. > Give a hobbit a ring and he eats fish for an age. >
