Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with auto-increment
Search options answers only
not deleted
user 7788
Numerical sequence generation for automatic key creation
3
votes
Accepted
Postgres CYCLE and existing values
The sequence will return values in order, whether or not they exist in the table. Your code will need to defend against that. Any method to defend against possibly already-in-use serial values will re …
- 57.3k
6
votes
Primary key with randomly varying increments (so it cannot be guessed easily)
As your goal is for:
the end users to not able to guess the primary keys by simply incrementing numbers.
then rather than just a variable increment of your keys (so they have to search a few ten …
- 57.3k
9
votes
Accepted
Auto increment char varying column prefixed with some characters
PostgreSQL does not have "auto-increment" fields in the sense of MySQL's AUTO_INCREMENT, but I'm guessing you mean SERIAL.
If so, yes, what you describe is possible, but please, please don't do this. …
- 57.3k