Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>In short: go for it. I doubt there's little to lose, but much to gain. </p> <p><em>The pros:</em></p> <p>**Good karma*</p> <p>never a bad thing to have.</p> <p>**More attention to our website*</p> <p>possibly a con if your code is <em>really</em> bad :)</p> <p>**Perhaps getting fixes and improvements from others*</p> <p>this is possibly the best thing you get from open-sourcing your code. Its all about sharing and helping each other, you get to use other's code, they get to use yours and everyone's gained from the trade.</p> <p><em>The cons:</em></p> <p>**Without investing more development, the tools might make us look bad*</p> <p>I'd search through to remove dodgy/rude/stupid comments, tidy up the formatting etc. </p> <p>**Publishing of the code requires some effort*</p> <p>requires barely any effort - set up an account in Sourceforge, create a <a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Subversion" rel="nofollow noreferrer">SVN repo</a> there and import your code. Then create a binary package (a zip file will do) and <a href="https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download" rel="nofollow noreferrer">release it</a> using the website. Might take you an hour, if you stop to read all the documentation.</p> <p>**Some of the tools might be too specialized for our needs*</p> <p>You could set the whole lot up as a group - eg PowerBuilder Tools, then people who see the really specialised tools won't have wasted their time getting them, they'll still have the 'more readily useful' tools.</p> <p>**The whole effort might go unnoticed given the shrinking community*</p> <p>Possibly, but then there's really no reason not to release the code. If you don't it may get completely lost to everyone when/if you change development tools.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs contributing internal tools to open source worth the effort?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USgbjbaanb
    1. USgbjbaanb
    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
    1. This table or related slice is empty.
 

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