Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>For some aspects of your problem, this might be relevant: <a href="http://en.wikipedia.org/wiki/DLL_hell#Running_Conflicting_DLLs_Simultaneously" rel="nofollow noreferrer">http://en.wikipedia.org/wiki/DLL_hell#Running_Conflicting_DLLs_Simultaneously</a>.</p> <p>Another common solution to this problem is to write an encapsulation layer on top of the functionality needed, which at least protects your code from wild changes when upgrading to new versions of supporting libraries.</p> <p>As to open source project lifetime, it should be clear which projects are healthy and which are not. For example, a project that is part of the Apache or Eclipse foundations are probably healthy, whereas some random thing on sourceforge is probably not. Generally, you can avoid this problem altogether by avoiding projects that do not seem active.</p> <p>For the negatives to copying code into your project:</p> <ol> <li>I know you wanted to put license aside, but you cannot in reality. I am not a lawyer and you should consult with one for your project if there may be issues, but if you are developing a proprietary system it could become GPL'ed accidentally.</li> <li>It makes your development environment more cluttered. You have to worry about making sure the copied-in code ompiles properly, is being compiled with the right version, and has the right build scripts. You also have all this extra code in your IDE that takes up space.</li> <li>As you pointed out, it makes updating code very difficult.</li> <li>If you have to file bugs with the Open Source project, it becomes more difficult to do. </li> <li>If you're not careful, a junior developer who doesn't know any better could go into the code and start mucking around with it.</li> </ol> <p>There's probably more reasons not to do it, but that's a few. Hope that helps.</p>
    singulars
    1. This table or related slice is empty.
    1. POCopy Paste vs. Reference
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJames Kingsbery
    1. USJames Kingsbery
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCopy Paste vs. Reference
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COCan you, or anyone, comment more on reasons NOT to just incorporate the source code for open source frameworks into your own source code?
      singulars
      1. PO
      1. USJeff
    2. COOK, added some reasons. Good Luck!
      singulars
      1. PO
      1. USJames Kingsbery
 

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