Databases
StackOverflow2013
Usersdbo
USssmith
 

Note that there are some explanatory texts on larger screens.

plurals
  1. USssmith
    primarykey
    data
    text
    plurals
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow do I Unit Test NServiceBus.Configure.WithWeb()?
      1. USssmith
      1. VTFavorite
    2. VO
      singulars
      1. PORendering directed graphs in a browser
      1. USssmith
      1. VTFavorite
    1. COAdding to last comment - if B is a third party or framework library, then you might write some "fixing" tests that document your assumptions about how it works, and then if/when you upgrade or replace B, you'll be informed by these tests if your assumptions about its behavior have changed. But the key point is that your unit tests should be testing your code, not the code your code depends on.
      singulars
      1. PO
      1. USssmith
    2. COIf B throws a NotAPrimeNumberException in response to a given parameter, then I would absolutely have a test for this in my suite of tests around B. I would not try and test B's behavior through a consumer of B (such as A, assuming A calls B). In A, I might test what A does if B throws an exception - that's testing A's behavior. I would not test, in A, that B actually does throw an exception under certain circumstances, as that is now testing B's behavior, not A's (and we have tests around B for that).
      singulars
      1. PO
      1. USssmith
    3. COYou answered your question with your comment. Your unit tests should document "all of the behavior of my method" and *not* the behavior of methods your method might call. As long as you're doing that, you're good. If it's important whether or how your method handles exceptions bubbling up to it, it's easy (using mocks or fakes) to set up a test where an exception is thrown to your method, and to verify it does the right thing with it. If that's important behavior, it seems valid to me as a unit test. But mock the interaction, don't rely on a particular other method implementation.
      singulars
      1. PO
      1. USssmith
 

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