Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Because stored procedures:</p> <ul> <li>add another development language, increasing complexity and potentially redundant code (logic written in both languages);</li> <li>generally have worse tooling, monitoring and debugging capabilities than PHP, C#, Java, Python, etc;</li> <li>are generally less capable than most middle tier languages;</li> <li>only have an advantage with high volume data transformation (where you avoid the server roundtrip), which tends to only be a minimum of actual usage.</li> </ul> <p>That being said, it's a common methodology on C# ASP.NET applications.</p> <p>As Jeff Atwood put it, <a href="http://www.codinghorror.com/blog/archives/000117.html" rel="noreferrer">stored procedures are the assembly language of databases</a> and people don't tend to code in assembly language unless they need to.</p> <p>I've frequently used materialized views and sometimes used CONNECT BY in Oracle, neither of which I believe exist in MySQL.</p> <p>I don't tend to use XML/XSLT in the database because, well, that means I'm using XML and XSLT.</p> <p>As for geographical or spatial data structures, the reason there is probably that they're hard to just "pick up". It's a fairly specialist area. I've read the MySQL manual on spatial data structures and I'm sure it makes sense to someone with extensive GIS experience but to me and my limited needs (which tend to be around marking the latitude/longitude of a point) it just doesn't seem worth the time investment to figure it out.</p> <p>Another issue is that if you go beyond ANSI SQL (much) then you've just tied yourself somewhat to a particular database vendor and possibly to a specific version. For that reason you'll often find application developers will tend to treat their databases at the lowest common denominator, which means treating them as a dumping ground for relational data.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy are database features being ignored, and instead reinvented in the middle tier?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. UScletus
    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. COI'd add the fact that stored procedures are rarely placed under source control.
      singulars
      1. PO
      1. USMusiGenesis
    2. COWell, that might be true but there's no reason they *couldn't* be put under source control.
      singulars
      1. PO
      1. UScletus
    3. COAll our sps are under source control, that's an excuse not a reason
      singulars
      1. PO
      1. USHLGEM
 

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