Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First, since you're using SQL Server and you can use stored procedures, don't use a trigger. It's not necessary. If your teacher needs justification, here's an <a href="http://www.sqlpass.org/LinkClick.aspx?fileticket=bX8_hcbYJ7U%3d&amp;tabid=236&amp;mid=1275" rel="nofollow noreferrer">article from SQL Server MVP Tom LaRock which discusses issues with handling triggers</a>.</p> <p>Second, as far as how to write the stored procedures, think about how to handle all the functionality logically. You've said you need to do the following:</p> <ul> <li>Read existing hurricane information</li> <li>Update existing hurricane information</li> <li>Insert a new hurricane into the database</li> </ul> <p>Your application should handle all of those as separate paths. And you need to think about the functionality before you write your first bit of T-SQL code. That means you have to have an interface which presents existing information. You're going to have to display the hurricanes existing in the database. Then once the user selects the one to get more information on, you'll have to pull back the hurricane history information. So I know in that situation I have two different data retrievals based on user input. That tells me I need to build the GUI interface to handle that progression logically and display the information in a way the user can use. And it also tells me I've got to build two different stored procedures. The second one will be passed some information identifying the hurricane to retrieve data on (which would be the primary key).</p> <p>Now roll through the rest of the application's functionality. That should get you started.</p>
    singulars
    1. This table or related slice is empty.
    1. POHelp me with my SQL project (please)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USK. Brian Kelley
    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. 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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThank you for advising me on stored procedures, moving away from triggers should shake up the class pretty good :D. I'm in high-school, by the way.
      singulars
      1. PO
      1. USJoel M.
    2. COA Teacher may have reasons to ask for triggers in particular, perhaps to illustrate how to use them. Not saying triggers are appropiate in this case or not, just sayin' with school assignments things are bit more blur.
      singulars
      1. PO
      1. USRemus Rusanu
    3. CORemus makes a good point. If you're required to use triggers, then you need to look at how to do so. Reading Tom's article will help. But otherwise, I think most of us would prefer to have the update logic in the stored procedures rather than in triggers.
      singulars
      1. PO
      1. USK. Brian Kelley
 

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