Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Handle your dependencies with care. They can bring you much speed, but can be a pain to maintain down the road. Here are my thoughts:</p> <ul> <li>Use some software to maintain your dependencies. Maven is what I would use for Java to do this. Without it you will very soon loose track of your dependencies.</li> <li>Remember that the various libraries have different licenses. It is not granted that a given license works for your setting. I work for a software house and we cannot use GPL based libraries in any of the software we ship, as the software we sell are closed source. Similarly we should avoid LGPL as well if we can (This is due to some intricate lawyer reasoning, don't ask me why)</li> <li>For unit testing I'd say go all out. It is not the end of the world if you have to rewrite your tests in the future. It might even be then that that part of the software is either extremely stable or maybe not even maintained no more. Loosing those is not that big of a deal as you already had a huge gain of gaining speed when you got it.</li> <li>Some libraries are harder to replace later than others. Some are like a marriage that should last the life of the software, but some other are just tools that are easily replaceable. (Think Spring versus an xml library)</li> <li>Check out how the community support older versions of the library. Are they supporting older versions? What happens when life continues and you are stuck at a version? Is there an active community or do you have the skill to maintain it yourself?</li> <li>For how long are your software supposed to last? Is it one year, five year, ten year or beyond? If the software has short time span, then you can use more to get where you are going as it is not that important to be able to keep up with upgrading your libraries.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POShould I be concerned with large number of dependencies?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USKnubo
    1. USKnubo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POShould I be concerned with large number of dependencies?
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 for Check out how the community support older versions of the library.
      singulars
      1. PO
      1. USstacker
    2. COUsing an LGPL licensed library is perfectly fine for a closed-source corporate setting. Many lawyers don't understand that, though. Frustrating.
      singulars
      1. PO
      1. USMike Clark
    3. COI am not a layer, but as I understand it the problem lies in the upgrade clause of the library (in a minor version way when it is binary compatible). We as a supplier of the software must allow the user to upgrade a library and still be compatible. If we don't comply with this we are breaking the terms of the license, and this could be a major pain when distributing the software.
      singulars
      1. PO
      1. USKnubo
 

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