Thank you Tom, I'll check it out. But I must say that I have many other functions using numeric fields and working well. This error has been rising up since I converted my fields from double precision to numeric. May be the problem is in my ODBC settings but I'm sceptic a bit about this. I had set the "Int8 As numeric" option before converting my fields.
Anyway, I subscript pgsql-odbc list. Thank you very much. -- Csaba ----- Original Message ----- From: "Tom Lane" <[EMAIL PROTECTED]> To: "Együd Csaba" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, July 02, 2003 6:23 PM Subject: Re: [GENERAL] Stored Proc error after modifying field type > =?iso-8859-2?Q?Egy=FCd_Csaba?= <[EMAIL PROTECTED]> writes: > > alumil=# \df addincominginvoice > > List of functions > > Result data type | Schema | Name | > > Argument data types > > ------------------+--------+--------------------+------------------------- -- > > --------------------------------------- > > integer | public | addincominginvoice | integer, integer, text, > > text, text, text, integer, text, text, text, text, numeric > > (1 row) > > > 31 17:59:12 SQL Error: PostgreSQL - ERROR: Function > > addincominginvoice(integer, integer, "unknown", "unknown", "unknown", > > "unknown", integer, "unknown", "unknown", "unknown", "unknown", double > > precision) does not exist > > IIRC, there's no implicit cast from double precision to numeric, only > the other direction. You'll need to do something to persuade the ODBC > driver to select numeric not float as the parameter type. This is > outside my field --- you might get some help in pgsql-odbc. > > regards, tom lane > > > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.491 / Virus Database: 290 - Release Date: 2003. 06. 18. ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
