Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would personally go for functional naming. The short reason: it avoids code duplication or dependency nightmare.</p> <p>Let me elaborate a bit. What happens when you are using an external jar file, with its own package tree? You are effectively importing the (compiled) code into your project, and with it a (functionally separated) package tree. Would it make sense to use the two naming conventions at the same time? No, unless that was hidden from you. And it is, if your project is small enough and has a single component. But if you have several logical units, you probably don't want to re-implement, let's say, the data file loading module. You want to share it between logical units, not have artificial dependencies between logically unrelated units, and not have to choose which unit you are going to put that particular shared tool into.</p> <p>I guess this is why functional naming is the most used in projects that reach, or are meant to reach, a certain size, and logical naming is used in class naming conventions to keep track of the specific role, if any of each class in a package.</p> <p>I will try to respond more precisely to each of your points on logical naming.</p> <ol> <li><p>If you have to go fishing in old classes to modify functionalities when you have a change of plans, it's a sign of bad abstraction: you should build classes that provide a well defined functionality, definable in one short sentence. Only a few, top-level classes should assemble all these to reflect your business intelligence. This way, you will be able to reuse more code, have easier maintenance, clearer documentation and less dependency issues. </p></li> <li><p>That mainly depends on the way you grok your project. Definitely, logical and functional view are orthogonal. So if you use one naming convention, you need to apply the other one to class names in order to keep some order, or fork from one naming convention to an other at some depth.</p></li> <li><p>Access modifiers are a good way to allow other classes that understand your <em>processing</em> to access the innards of your class. Logical relationship does not mean an understanding of algorithmic or concurrency constraints. Functional may, although it does not. I am very weary of access modifiers other than public and private, because they often hide a lack of proper architecturing and class abstraction.</p></li> <li><p>In big, commercial projects, changing technologies happens more often than you would believe. For instance, I have had to change 3 times already of XML parser, 2 times of caching technology, and 2 times of geolocalisation software. Good thing I had hid all the gritty details in a dedicated package...</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POWhat strategy do you use for package naming in Java projects and why?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USVarkhan
    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. COForgive me if I'm wrong, but it sounds to me like you're more talking about developing a framework that's intended to be used by many people. I think the rules change between that type of development and developing end user systems. Am I wrong?
      singulars
      1. PO
      1. USTim Visher
    2. COI think for common classes used by many of the vertical slices, it makes sense to have something like a `utils` package. Then, any classes that need it can simply depend on that package.
      singulars
      1. PO
      1. USTim Visher
    3. COOnce again, size matters: when a project becomes big enough, it needs to be supported by several people, and some kind of specialization will occur. To ease interaction, and prevent mistakes, segmenting the project in parts becomes quickly necessary. And the utils package will soon become ginormous!
      singulars
      1. PO
      1. USVarkhan
 

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