Safe? If there is no possibility that any two rows can have the same time.
If so, then its safe.
The better question is: Is the data in that row in that table defined by the
timestamp? or by another column, or combination of columns in the table? Or
possibly they only need a sequence number to id
Hi,
Thank you all for anwering me preious question. I am hope ful that I will
get answer for my next one also.
I want to know if it is safe enough to use a field with "timestamp" type as
primary key for a table.
Will it cause any problem while processing muiltple requests?
with regards
Rajeev
Thanks Steve and Roberts,
Yes its really tricky,
With regards
Rajeev Rumale
**
"The human race has one really effective weapon, and that is laughter."
**
Log is as follows:
/u01/app/oracle/admin/tmp/DBD/DBD-Oracle-1.09 #perl Makefile.PL
Using DBI 1.20 installed in
/opt/perl5/lib/site_perl/5.6.0/PA-RISC1.1/auto/DBI
Configuring DBD::Oracle ...
>>> Remember to actually *READ* the README file!
Especially if you have any problems.
Usin
On Sat, 1 Sep 2001, Alex Krohn wrote:
> > my $dbh = DBI->connect("DBI:Pg:dbname=test", "postgres", "");
> > my $val = $dbh->quote(q!\'?:!);
> > print "val: $val\n";
> > my $sth = $dbh->prepare("INSERT INTO foo (a) values ($val)");
> Placeholders isn't really an op
On Wed, 29 Aug 2001, Alex Krohn wrote:
> If I use mysql, or Oracle, as a driver, it works as expected. I searched
> through the list, and the only answer seemed to be to use placeholders,
> which isn't really an option in my situation.
Why are placeholders not an option? They're generally a goo
On Sat, 01 Sep 2001 17:14:34 -0700, Alex Krohn wrote:
>the following works
>of course:
>
> my $sth = $dbh->prepare ('INSERT INTO foo (a) VALUES ("hello?")');
It does? Yet IMO it should have been
my $sth = $dbh->prepare ("INSERT INTO foo (a) VALUES ('hello?')");
Check out the quote
