Thanks for the reply Peter..
you are right in the case of synthetic primary key using a sequence. We already planned this way, as the LAST Option.
But we believe in the long form of date, as we can get Nano seconds of the hit, by using java.sql.Timestamp class, we are hopeful that we can get the solution in some way.
But we came to notice that, when i apply MY PROBLEM for creating ordinary objects in a standalone program using below code, nano seconds concept also doesnt work.
import java.util.Date;
import java.sql.Timestamp;
public class TimeStampNanoSeconds
{
public static void main(
String[] args)
{
Date d=new Date();
Nano(d);
}
public static void Nano(Date date)
{
Timestamp ts=new Timestamp(date.getTime());
System.out.print(date.getTime());
System.out.println("\tNano==="+ts.getNanos());
Date d1=new Date();
Nano(d1);
}
}
but we are hopeful that we will get a UNIQUE "long" number when it is in the case INSERTION into database table or any other databse transactions.
AM I confusing anybody?? if so, dont hesitate to clarify with me...
Many Thanks One and All,prasadbh.
