Remember: Although OID is somewhat unique (as others have
mentioned), the OID isn't entirely unique. Once it reaches
the extent of the datatype it will go back to 0 and start
again.
I suggest either using transactions or have another set of
identifiers which you can use together to identify the
inserted row... such as user_id and timestamp (which you've
manually created, not using NOW)... If it's for something
human based, a user would not be able to realistically click
two submit buttons in the same second... if you do get that
happening, then maybe you could assume it was spam.
Just a thought
----
Server IP: 66.163.161.117
Probable Submitter: 192.100.124.218 (proxied:
172.26.134.171, 172.26.130.89)
----
X-Spam-Status: No, hits=3.1 required=5.0
tests=DATE_MISSING,FROM_NO_LOWER
autolearn=no version=2.64
----
Manual Page -- http://www.php.net/manual/en/function.pg-last-oid.php
Edit -- http://master.p
hp.net/note/edit/66894
Del: integrated -- ht
tp://master.php.net/note/delete/66894/integrated
Del: useless -- http:
//master.php.net/note/delete/66894/useless
Del: bad code -- http
://master.php.net/note/delete/66894/bad+code
Del: spam -- http://m
aster.php.net/note/delete/66894/spam
Del: non-english -- h
ttp://master.php.net/note/delete/66894/non-english
Del: in docs -- http:
//master.php.net/note/delete/66894/in+docs
Del: other reasons-- http://master
.php.net/note/delete/66894
Reject -- http://master
.php.net/note/reject/66894
Search -- http://ma
ster.php.net/manage/user-notes.php
--
PHP Notes Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub
.php
|