I got following question on an interview:
Which SQL mechanisms allow user to browse tables sequentially?
I got following question on an interview: Which SQL mechanisms allow user to browse
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I got following question on an interview:
Which SQL mechanisms allow user to browse tables sequentially?
Cursor is a good example – but I don’t think you could really argue that Cursors are truely a part of SQL – rather they just tend to come bolted in with procedural languages used on database servers – like pl/SQL and T-SQL.
You could also make an argument for Recordsets, Dynasets, DataTables and DataViews, but those aren’t part of SQL itself either.
They might be referring to ORDER BY with a sequential field on the table, but if so, they’ve not phrased their question very well…
Martin.