Hi,

I've recently been 'bitten' by the placeholder feature in selects.

While I certainly appreciate that placeholders are a good way of reducing the workload for large selects, etc., what I'm actually after is a way of turning the placeholder feature completely off within the DBI module, if it's at all possible.

I'm using DBI / DBD::Pg and finding that the placeholders are being interpreted in places where I'd rather them not.

At the moment I've got a system whereby a user inputs some data which is collated into a record that also includes several values that are auto-created by other components of a system.

In order to then determine and provide to the user the details that have been auto-created I do a select based on the recently input record parameters that the user provided. Unfortunately if some of the content includes character combinations that can be interpreted to be placeholders, which is where the select then becomes unstuck, because it's not really trying to do a placeholder style select...

I could if I really had to completely change the system so that it works out the auto-created values first and then does the insert but that's a lot of work, so before I decide that I absolutely have to do this I'm hoping that someone will answer with a simple variable in the DBI module that I've over-looked that turns off placeholders (if that's possible).

Any thoughts/suggestions would be most appreciated. I'm currently using DBI v1.3 and have just downloaded DBI 1.32 to try but I can't see anything in the changes between 1.3 and 1.32 that reference placeholders...

I've had a quick search of a couple of the DBI mailing list archives suggested but was not able to find anything discussing the disabling of placeholders.

Cheers,

-Preston.

--
Preston de Guise [EMAIL PROTECTED]
[EMAIL PROTECTED] 02 9900 2100 switch
www.enstor.com.au 02 9900 2199 fax
ENSTOR - Enterprise Storage Solutions
1 8000 ENSTOR - Service/Support Call Hotline 1800 036 786 fix

Reply via email to