Re: ... something in the environment?

Maybe the problem hides in the omitted part of your code. There is no declaration shown for $p1 to $p9 and you don't have a problem when bind_param is called with these variables.

Just a guess...
-jo

Comment on Re: ... something in the environment? Select or Download Code

Replies are listed 'Best First'.
Re^2: ... something in the environment? by chexmix (Hermit) on Feb 27, 2020 at 21:50 UTC
Thanks. I should have said (and did in a previous incarnation of this post, lost when my work comp temporarily died!) that $p1 - 9 are parameters that are passed in to the subroutine this is in. So they're all initialized. Maybe I should be concerned that I DIDN'T get 'uninitialized value' messages in my testing environment ...? I'm really stumped. I have found what I thought was an obvious solution to this three times or so. Also, if it matters, the full complaint is "Use of uninitialized value in subroutine entry at <script> <line number>".	[reply]
Re^3: ... something in the environment? by bliako (Abbot) on Feb 27, 2020 at 22:58 UTC
this is beyond my ability but can I assume that this is XS related? That is, it comes from within the db driver? Or simpler explanation: the db stores some illegal values or undef? This is what made me think that: Re: Source of warning message: "Use of uninitialized value in subroutine entry". (that post has cult value too) bw, bliako	[reply]
Re^2: ... something in the environment? by chexmix (Hermit) on Mar 03, 2020 at 16:52 UTC
A big thank you to all who responded. I haven't been able to get to the bottom of this yet -- and have been asked to stop trying until a later date. When I fix the issue I will post the fix. I haven't been on here much of late and had forgotten what a great community it is. Glenn	[reply]