this takes a resultset containing two columns . column 1 contains the function name , column 2 the oid . it reads the entire resultset , loading the values into the function table . remember to close the resultset after calling this !! implementation note about function name lookups : postgresql stores the function id 's and their corresponding names in the pg_proc table . to speed things up locally , instead of querying each function from that table when required , a hashmap is used . also , only the function 's required are entered into this table , keeping connection times as fast as possible . the org.postgresql.largeobject.largeobject class performs a query upon it 's startup , and passes the returned resultset to the addfunctions method here . once this has been done , the largeobject api refers to the functions by name . dont think that manually converting them to the oid 's will work . ok , they will for now , but they can change during development there was some discussion about this for v7 .0 , so this is implemented to prevent any unwarranted headaches in the future . concode_field_sep long NUM_OIDS concode_elem_sep QueryExecutor executor concode_elem_sep Map<String,Integer> func concode_elem_sep BaseConnection connection concode_field_sep long getLong concode_elem_sep void addFunction concode_elem_sep Object fastpath concode_elem_sep byte[] fastpath concode_elem_sep Object fastpath concode_elem_sep byte[] fastpath concode_elem_sep int getInteger concode_elem_sep int getID concode_elem_sep FastpathArg createOIDArg concode_elem_sep long getOID concode_elem_sep byte[] getData
void function ( ResultSet arg0 ) { while ( arg0 . next ( ) ) { func . put ( arg0 . getString ( 1 ) , arg0 . getInt ( 2 ) ) ; } }