search for: 01861

..."INSERT into DATEST (CDATE) VALUES ( :1 ) ", bind=c( "character")) ## -- c("date") does not work sapply(d, class) d$CDATE <- as.character(d$CDATE) sapply(d, class) dbExecStatement(ps,d) Error in oraExecStatement(ps, data, ...) : RS-DBI driver: (ORA-01861: literal does not match format string ) Thanks for your help in advance, Swami (smalladi at lexgen.com) ----------------------------- Correspondence with David James ----------------------- Dear David, Thanks for your kind reply. I did what you suggested, coerced d into a character vector. Now...

We are using MFC/R2 driver successfully in at least three places in Brazil. I have problem with an Asterisk integrated with MFC/R2 with a Siemens Hicom 300. I can get a good audio quality with Grandstream, Polycom, and X-Lite softfones, but SIPURAS and Linksys get a garbled audio, something like a "Darth Vader" voice. We have tried everything in Sipura. The SIPURA 2000 and the Linksys

I''m seeing a behavior in Rails that I find very strange. Having worked quite a bit with Oracle with other languages I would always dutifully do ALTER SESSION SET NLS_DATE_FORMAT = <my_date_format> and ensure I use that date format in my application. With Rails I still have not figured out how to execute an ALTER SESSION statement after connecting to the database (I''m using

...exec'' c:/ruby/lib/ruby/gems/1.8/gems/activerecord-oracle- adapter-1.0.0.9250/lib/active_record/connection_adapters/ oracle_adapter.rb:229:in `next_sequence_value'' app/controllers/datafile_controller.rb:248:in `approval'' However what the real problem was is this: ORA-01861 Literal Does Not Match Format String As it turns out (and after lots of research and unless I am crazy already) the problem seems to be in the INSERT statement that is generated. Here goes an example (edited with just some date and datetime values): INSERT INTO (...) VALUES(''2011-01-01...