Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The RSS feed doesn't have random IDs. You are inserting a random ID, which you want to not be random. (I don't even know why you want an ID.) </p> <p>If you just take the numbers from their guid, you would have a unique ID that will serve your needs. All you have right now is a fake ID.</p> <p>Added: IDs are very rarely 'random' in any sensible project. You want an ID that stays the same. Presumably, you also do not want two stories to have the same ID. Therefore what you need is not a random number, but to assign a random-looking number to each new entry. </p> <p>You cannot do this without a database (although you could use a flat file database). The table needs two columns - 'ArticleID' and 'RandomID'.</p> <p>You need to find an item in the feed that is unique and does not change, so that you can recognise it again. News titles do change, so the numbers in the BBC's GUID should be your best bet.</p> <p>What you then need to do is take this ArticleID number and DB query for a matching row to get an existing RandomID. If there isn't one, keep generating a random number in your current fashion and checking to see if the RandomID is already used until you find a new unused random number. Then insert a new row with ArticleID and RandomID, using the new RandomID for whatever crazy purpose you have.</p> <p>You could also generate a set of unused random numbers ahead of time. You may also wish to introduce a datestamp or an auto-increment ID so you could more easily delete old article/randomID combinations when eventually necessary.</p>
    singulars
    1. This table or related slice is empty.
    1. POAssigning a random number to a title which stays the same
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaul Gregory
    1. USPaul Gregory
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COHi Paul, for my purpose the ID has to be random.
      singulars
      1. PO
      1. USSam W
    2. COOr, more accurately, have been randomly generated. Updated to outline a methodology.
      singulars
      1. PO
      1. USPaul Gregory
    3. COThanks for your time on this Paul, the ideas you've put forward are very interesting. I'm going to attempt to generate a set of random unused numbers. Thanks again!
      singulars
      1. PO
      1. USSam W
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload