Command window: PLD substitutes the variable &&1 with the text "Developer\login.sql"

[Claus Pedersen]

I have a command script with the commands:
SELECT &&1 FROM dual;
SELECT &&2, &&1 FROM dual;

PLD does not prompt for the variable &&1, but instead automatically replaces it with the text

Developer\login.sql

so my first select becomes

SELECT Developer\login.sql FROM dual

PLD prompts for variable &&2 correctly: Enter value for 2.

If I enter e.g. '?' in the prompt for 2, my second select becomes:

SELECT '?', Developer\login.sql FROM dual

Where does this "Developer\login.sql" string come from and what do I do to get rid of it? Does &&1 have a special meaning in PLD?

I am using PLD version 11.0.6.1776 32 bit.

The 64 bit version also sometimes gives this error, but only when you call command scripts from other command scripts (at least that is the situation where I have noticed it)

 

[clarnate]

I am having the same problem. It only started happening last week. Prior to that it would ask me to enter the value...

 

[Gustavo]

I can reproduce it with PLD 11.0.5.1775.

 

[Marco Kalter]

We'll fix it.

 

[Claus Pedersen]

Thanks.

Do you have a scheduled date for the next release?

 

[Marco Kalter]

It will be version 12.0. We'll have a public beta in about a month.

 

[Claus Pedersen]

OK, you will not publish more patches to version 11 before that? It is a problem that is troubling us a lot, and from the first beta version and to the final version 12 will be maybe a month and

 

[Claus Pedersen]

OK, you will not publish more patches to version 11 before that? It is a problem that is troubling us a lot, and from the first beta version and to the final version 12 will be maybe a month and 1/2. So realistically, it will not be fixed before November or December.

A patch fix to version 11 within the next month would be very much appreciated.

 

[Marco Kalter]

Okay. We'll provide a patch as soon as we fix this.

 

[Marco Kalter]

Can you try this patch and let me know if this fixes the issue?

 

[Claus Pedersen]

It worked, thanks.

Did you find out why it sometimes failed in the 64 bit version? So it can be fixed here as well.

 

[Marco Kalter]

Not yet. If you have a reproducible case, let me know.