Hi, last time I checked, IBExpert used the last parameter as reference, so it'll use a varchar(1)/char(1) . I followed the same pattern for the IBPP library bundled with Flamerobin when I added named parameters support, I wanted to convert correctly the parameter to its appropriate data type but lacked proper time and knowledge in C++ to guarantee every possible conversion properly so opted to keep it simple:\ At least from my previous tests with Delphi some component access automatically convert each time to its specific data type, no sure about other languages I could say each library uses a behavior they choose.
On Wed, Aug 17, 2022 at 11:03 PM Adriano dos Santos Fernandes < adrian...@gmail.com> wrote: > Hi Mark, Jiri, all! > > How are client libraries (Jaybird, .NET Provider, Delphi ones) > describing its named parameters to their users? > > I mean, given this SQL: > > select * > from rdb$database > where :param = 1 or :param = '2' > > We have here single name used in context with multiple types. > > I suppose you transform this to: > > select * > from rdb$database > where ? = 1 or ? = '2' > > Which will map to two Firebird parameters with different types. > > But for the user of the library, I suppose it's one parameter, correct? > > And what type (and the deduction rules) this parameter will be described > as? > > > Adriano > > > Firebird-Devel mailing list, web interface at > https://lists.sourceforge.net/lists/listinfo/firebird-devel >
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
