Hi We need to make it database agnostic so we can't have oracle specific sql functions in there.
However we should be able to add a row with created_timstamp and use a java.util.Date object type. JPA should be able to map that to any database. On Mon, Apr 4, 2011 at 5:13 PM, Christian Müller <christian.muel...@gmail.com> wrote: > Hello list! > > I'm thinking about to add a timestamp property to the idempotent repository > (at least to the JDBC and JPA based one). The reason is the following: > The individual records in our batch file doesn't have a unique id which we > can use as key for the idempotent consumer. Our solution was to get the > entire line and build a hash for the key. > The problems comes, after we have been asked to remove the entries in the > idempotent repository from the last processed file, because it should be > processed again. We could not do this, because we don't know which entries > (hashes) belongs to the last file we processed. > Our short time solution is to extend the database table we use and add a > 'created_at' column which is filled by the database with a default value to > 'sysdate' (Oracle). I'm wondering whether we should support this by default > in further versions of Camel (set the created_at timestamp) at least in the > JDBC and JPA based idempotent repositories. > > What you are thinking? > > Cheers, > Christian > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com CamelOne 2011: http://fusesource.com/camelone2011/ Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
