Re: PostgreSQL 8, JDBC 8 and JSTL problems
От | Oliver Jowett |
---|---|
Тема | Re: PostgreSQL 8, JDBC 8 and JSTL problems |
Дата | |
Msg-id | 42B9F96B.7000901@opencloud.com обсуждение исходный текст |
Ответ на | PostgreSQL 8, JDBC 8 and JSTL problems (Donny Tjandra <dtjandra@pcthome.com>) |
Список | pgsql-jdbc |
Donny Tjandra wrote: > <sql:query var="properties"> > select * > from get_property_rates(?,?,?,?) > > <sql:param value="${firstDate}"/> > <sql:param value="${lastDate}"/> > <sql:param value="${brandLocationId}"/> > <sql:param value="1"/> > </sql:query> > > Unfortunately the type mapping somewhere between JSTL, JDBC and > PostgreSQL is broken and I get function not exist errors like: > > ERROR: function get_property_rates(character varying, character varying, > integer, character varying) does not exist. > All this worked fine with PostgreSQL 7. I'm not sure how many others out > there run into this issue and how they get around it (maybe create > wrapper functions that takes all text parameters), or if there are plans > to add smarter type mapping in future versions of the driver. Search the archives -- it's not really practical to add "smarter type mapping" (really, less strict typing) at the driver level. The "right fix" is to fix the parameter types being given to JDBC by the JSTL layer. I'm not familiar with JSTL -- does <sql:param> let you specify a parameter type? At the JDBC level you can, so I suppose you can in JSTL. BTW it's a driver change, not a backend change, that changed parameter typing behaviour between 7.x and 8.x, so if you are going to revert you should only need to revert the driver. -O
В списке pgsql-jdbc по дате отправления: