umm, you use bind variables for performance and because anyother way is a bug in your code!!!!!

but in jdbc, you just use prepared statements for this.

you would prepare a statement "update t set c1 = ?, c2 = ?, c3 = ?"

you would bind to it

you would execute it.


something like this:

static void doPreparedStatement (Connection con, int count)
throws Exception
{
long start = new Date().getTime();
PreparedStatement ps =
con.prepareStatement
("insert into testxxxperf " +
"(id, code, descr, insert_user, insert_date)"
+ " values (?,?,?, user, sysdate)");

for (int i = 0; i < count; i++)
{
ps.setInt(1,i);
ps.setString(2,"PS - code" + i);
ps.setString(3,"PS - desc" + i);
ps.executeUpdate();
}
long end = new Date().getTime();
con.commit();
System.out.println
("pstatement " + count + " times in " + (end - start) + " milli seconds");
}

you don't want to even consider doing that. it would be a really bad idea. Please stick with normal identifiers - you'll be really sorry otherwise.

PLEASE, BEGGING YOU, DO NOT GO DOWN THIS PATH

you will hate yourself, seriously, this is a really bad idea.


Just because there is an answer to a direct question does not mean it should be provided.

eg: do cats always land on their feet? That has a direct answer, however, if asked by a 5 year old kid, you might want to ask "why do you ask" before you consider answering. Since the answer could lead to the immediate death of an innocent cat as it is dropped from the balcony.


This is a cat question - it should not be answered.

I totally agree that just because something can be done technically, sometimes it is not advisable to do it.

i like that!

because many applications will not quote a username used in a connection. You'll find most applications, many applications are not able to connect.


quoted identifiers are a hugely bad idea in practice.