Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>IMVHO your colleague is kind of on the right track, but not quite.</p> <p>A good rule to follow is that you should never expose actual IDs in the query string, as that gives a clue as to the structure of your database, and makes it just that little bit easier for someone to carry out a SQL injection type attack (they can target specific records because they know the ID).</p> <p>So your colleague is attempting to achieve this, albeit in a very round-about way. Personally I wouldn't do it this way because it will simply be a matter of time before a smart attacker works out what you are doing and then works out what the magic number is. It also doesn't really do anything to prevent a SQL injection attack against specific records, as the generated number may match an existing key anyway. If you are <strong>relying</strong> on this methodology to avoid SQL attacks then you have deeper issues that need to be addressed.</p> <h2><strong>Edit</strong></h2> <p>Mentioning an alternative is probably a fair thing to do. As you are using C# and pulling parameters out of the querystring, I will assume you are using ASP.NET. In that case, important IDs can be kept in Session or the Cache. You can store a bunch of items in a custom data object, which you then store in Session (this saves having to keep track of lots of IDs, you just need to know one). ASP.NET manages the web app's Session for you, it is unique to each user, and you can use it to store stuff when you transition from page to page.</p> <p>If you are manually tracking session or using a database to keep your session related info then you can still serialize the aforementioned data object into the database using a generated GUID as its key, and append that GUID to the query string (there is only an incredibly low chance of success if a user messes with a GUID to try and assume someone else's session, you can lower that chance even further by concatenating two GUIDs as a key, etc.).</p>
    singulars
    1. This table or related slice is empty.
    1. POIs a Modification Number to mask an Id in a query string necessary?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USslugster
    1. USslugster
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs a Modification Number to mask an Id in a query string necessary?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COSeems like there are benefits to obfuscating your query strings then (to limit exposure of your DB structure), but there are also better techniques. http://www.4guysfromrolla.com/webtech/012000-1.shtml Thanks.
      singulars
      1. PO
      1. USplntxt
    2. COProvide an alternate methodology e.g. encryption and I'll happily accept your answer.
      singulars
      1. PO
      1. USplntxt
    3. CO@Jim, answer has been extended. Hope it helps.
      singulars
      1. PO
      1. USslugster
 

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