From: Nickolay S. <sk...@bs...> - 2002-11-26 12:28:33
|
Hello, Claudio ! Tuesday, November 26, 2002, 6:37:51 AM, you wrote: >> You should be able to query the client and ask it which version of the >> engine you are >> talking to. Then you know which way to process the params. > I requested the behavior to be configurable. Nickolay agreed as I > understand. In this case, I'm not sure if the engine version is going to > help. > Maybe there's a way to read the config params other than resorting to the > Services API? > ;-) Check for correct parameter order is simple. Issue query: -- select (select 'test' from rdb$database where 0=?) from rdb$database where 1=? -- with first parameter 0 and second 1. If you get a record you can depend on that parameter order and count ALWAYS matches SQL source string. Otherwise you'll have to resort to older tricks to workaround IB/FB1 bugs. What exactly were you talking about when describing parameter duplication ? If queries like this, when two extra paramters (of 4 total) were generated: -- select (select 'test' from rdb$database where 0=?) from rdb$database where 1=? group by 1 order by 1 -- than yes, I fixed this too. Lexer (parse.y), not pass1 compiler performs actiual parameter numbering and identification now. > C. -- Best regards, Nickolay Samofatov mailto:sk...@bs... |