From: <no...@so...> - 2001-03-19 17:00:56
|
Bugs item #409769, was updated on 2001-03-19 09:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769&group_id=9028 Category: Core Engine Group: None Status: Open Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: UDF argument can't be query-parameter Initial Comment: Query kind of: SELECT Field1, Field2, ... , UDF1(Field1, ?Param1) FROM TABLE1 don't work - message is "unknown data type" ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769&group_id=9028 |
From: <no...@so...> - 2001-08-15 01:29:49
|
Bugs item #409769, was opened at 2001-03-19 09:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769&group_id=9028 Category: Core Engine >Group: Initial Bug Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: UDF argument can't be query-parameter Initial Comment: Query kind of: SELECT Field1, Field2, ... , UDF1(Field1, ?Param1) FROM TABLE1 don't work - message is "unknown data type" ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769&group_id=9028 |
From: <no...@so...> - 2001-12-03 08:14:43
|
Bugs item #409769, was opened at 2001-03-19 09:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769&group_id=9028 >Category: DSQL >Group: Confirmed Bug Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Claudio Valderrama C. (robocop) Summary: UDF argument can't be query-parameter Initial Comment: Query kind of: SELECT Field1, Field2, ... , UDF1(Field1, ?Param1) FROM TABLE1 don't work - message is "unknown data type" ---------------------------------------------------------------------- >Comment By: Claudio Valderrama C. (robocop) Date: 2001-12-03 00:14 Message: Logged In: YES user_id=62823 Our syntax allows that. However, the DSQL layer doesn't retrieve information about parameters to know what their type is. A fix is being tested, but the interaction with descriptor-based UDFs will surprise developers. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769&group_id=9028 |
From: <no...@so...> - 2001-12-10 06:22:34
|
Bugs item #409769, was opened at 2001-03-19 09:03 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769&group_id=9028 Category: DSQL >Group: Fixed v1.0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Claudio Valderrama C. (robocop) Summary: UDF argument can't be query-parameter Initial Comment: Query kind of: SELECT Field1, Field2, ... , UDF1(Field1, ?Param1) FROM TABLE1 don't work - message is "unknown data type" ---------------------------------------------------------------------- >Comment By: Claudio Valderrama C. (robocop) Date: 2001-12-09 22:22 Message: Logged In: YES user_id=62823 Now it works. For this, the DSQL layer has to load information about UDF arguments that previously it didn't have available. With udfs that use descriptors, the recognized parameter type is always the formal parameter; the engine cannot guess the actual parameter wanted by the user. Either redeclare that udf with a different SQL name and use the desired formal parameter or try adjusting the scale of the input query parameter when the format argument is int and the current parameter is numeric(9,4), for example. If a UDF is declared to receive INT by descriptor, the engine can pass it happily a numeric(p,s) quantity, then it's to the udf to test the scale. ---------------------------------------------------------------------- Comment By: Claudio Valderrama C. (robocop) Date: 2001-12-03 00:14 Message: Logged In: YES user_id=62823 Our syntax allows that. However, the DSQL layer doesn't retrieve information about parameters to know what their type is. A fix is being tested, but the interaction with descriptor-based UDFs will surprise developers. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769&group_id=9028 |
From: Claudio V. C. <cv...@us...> - 2001-03-26 03:35:06
|
Hello, fellow members. This is not a bug. This is a known limitation, unless it worked before IB4. Do I close it or do change it to become a request for enhancement? C. > -----Original Message----- > From: fir...@li... > [mailto:fir...@li...]On Behalf Of > no...@so... > Sent: Lunes 19 de Marzo de 2001 13:03 > To: no...@so... > Subject: [Firebird-devel] [ firebird-Bugs-409769 ] UDF argument can't be > query-parameter > > > Bugs item #409769, was updated on 2001-03-19 09:03 > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769 > &group_id=9028 > > Category: Core Engine > Group: None > Status: Open > Priority: 5 > Submitted By: Nobody/Anonymous (nobody) > Assigned to: Nobody/Anonymous (nobody) > Summary: UDF argument can't be query-parameter > > Initial Comment: > Query kind of: > > SELECT > Field1, Field2, ... , > UDF1(Field1, ?Param1) > FROM > TABLE1 > > don't work - message is "unknown data type" > > > ---------------------------------------------------------------------- > > You can respond by visiting: > http://sourceforge.net/tracker/?func=detail&atid=109028&aid=409769 > &group_id=9028 |
From: Dmitry K. <di...@de...> - 2001-03-26 11:14:49
|
Hello, Claudio! "Claudio Valderrama C." wrote: > > Hello, fellow members. This is not a bug. This is a known limitation, unless > it worked before IB4. Do I close it or do change it to become a request for > enhancement? > > SELECT > > Field1, Field2, ... , > > UDF1(Field1, ?Param1) > > FROM > > TABLE1 > > > > don't work - message is "unknown data type" I saw this even if udf with param was used in WHERE clause. So it should be tested completely. Seems that 4.x and 5.x had better behavior than 6.0 in this area. p.s. thank you for gstat options info. -- Dmitry Kuzmenko, Epsylon Technologies. |
From: Claudio V. C. <cv...@us...> - 2001-03-27 05:13:40
|
> -----Original Message----- > From: fir...@li... > [mailto:fir...@li...]On Behalf Of > Dmitry Kuzmenko > Sent: Lunes 26 de Marzo de 2001 7:19 > > "Claudio Valderrama C." wrote: > > > > Hello, fellow members. This is not a bug. This is a known > limitation, unless > > it worked before IB4. Do I close it or do change it to become a > request for > > enhancement? > > > > SELECT > > > Field1, Field2, ... , > > > UDF1(Field1, ?Param1) > > > FROM > > > TABLE1 > > > > > > don't work - message is "unknown data type" > > I saw this even if udf with param was used in WHERE clause. > So it should be tested completely. Seems that 4.x and 5.x had better > behavior than 6.0 in this area. Are you suggesting that previous IB versions accepted parameters in UDF arguments? For me, even in v4, IB always refused to take things like udf_name(:param) Or did you succeed previously with such construction in the WHERE clause with IB5? C. |
From: Dmitry K. <di...@de...> - 2001-03-27 08:24:32
|
Hello, Claudio! "Claudio Valderrama C." wrote: > > I saw this even if udf with param was used in WHERE clause. > > So it should be tested completely. Seems that 4.x and 5.x had better > > behavior than 6.0 in this area. > > Are you suggesting that previous IB versions accepted parameters in UDF > arguments? For me, even in v4, IB always refused to take things like > udf_name(:param) > Or did you succeed previously with such construction in the WHERE clause > with IB5? Sorry, not with 5.x and don't remember about 4.x. I was using udfs with parameters since IB 4.0, but mostly in stored procedures like if ((LAND(:ARR, :ACT) <> 0) or ((:UID = :UI) and (LAND(:URR, :ACT) <> 0)) or ((:GID = :GI) and (LAND(:GRR, :ACT) <> 0))) then CANDO=1; else ... where ACT is input proc variable and URR/GRR are local proc variables (this works for 5.x). So I was wondered that where x = udf(field, :param) does not work in query. I think if it was not supported, it must be :-) It is very strange to support parameters for udf in procedures and do not support them for queries. The only workaround of this problem is to construct query at client side without parameter: .... Q.SQL.Add('select * from table'); Q.SQL.Add('where a = udf(b, '+IntToStr(paramval)+')'); Q.ExecQuery; ... -- Dmitry Kuzmenko, Epsylon Technologies. |