Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POWhich NetBeans projects files should go into source control?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USThomas Owens
    1. USThomas Owens
    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. COClearly not going to add build output (including JavaDocs). But I doubt the best answer is "none". Each developer would then need to setup common project settings locally, including simple things like which dirs are source, or what JDK level to build for. Not sharing that sort of project setup information would set us up for trouble. For example, I write code that works for 1.6 but our project ships for 1.5. I commit that, and break the build.
      singulars
      1. PO
      1. USPeter Cardona
    2. COWhen I import a project with Eclipse, it's trivial for me to identify source directories and the JDK to build for. Besides, there should be a build script that does that for me, since I might not be using an IDE at all (but rather a text editor - Notepad++, emacs, vim). Every job that I've ever had that used source control only committed source files and human-generated documentation to the repository and I've never seen a problem.
      singulars
      1. PO
      1. USThomas Owens
    3. COI don't agree with this. I think it makes things a lot easier if all devs on a project are using the same IDE and version. Project files should be checked in - it means each dev does not have to jump through hoops setting up their environemnt each time they need to work on the source. If everyone checks out projects and dependent projects and JARs into the same location or relative path structure then they should be able to checkout and click build in one step. Too much time wasted if everyone has to re-configure a project and fix broken dependencies all the time
      singulars
      1. PO
      1. USSteve Claridge
 

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