Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Stop thinking about technology (e.g. Java Portals, ColdBox modules, etc...) and focus on architecture. By this I mean imagining how you can explain your system to an observer. Start by drawing a set of boxes on a whiteboard that represent each piece - inventory, clients, issue tracking, etc... - and then use lines to show interactions between those systems. This focuses you on a <a href="http://en.wikipedia.org/wiki/Separation_of_concerns" rel="nofollow">separation of concerns</a>, that is grouping together like functionality. To start don't worry about the UI, instead focus on algorithms and data. </p> <p>If you we're talking about MVC, that step is focusing on the model. With that activity complete comes the hard part, modifying code to conform to that diagram (i.e the model). To really understand what this model should look like I suggest reading <a href="http://rads.stackoverflow.com/amzn/click/0321125215" rel="nofollow">Domain Driven Design</a> by Eric Evans. The goal is arriving at a model whose relationships are manageable via <a href="http://en.wikipedia.org/wiki/Dependency_injection" rel="nofollow">dependency injection</a>. Presumably this leaves you with a set of high level CFCs - services if you will - with underlying business entities and persistence management. Their relationships are best managed by some sort of bean container / service locator, of which I believe ColdBox has its own, another example is ColdSpring. </p> <p>The upshot of this effort is a model that's unit testable. Independent of of the user interface. If all of this is confusing I'd suggest taking a look at <a href="http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias=stripbooks&amp;field-keywords=Working%20Effectively%20with%20Legacy%20Code&amp;x=0&amp;y=0" rel="nofollow">Working Effectively with Legacy Code</a> for some ideas on how to make this transition. </p> <p>Once you have this in place it's now possible to think about a controller (e.g. ColdBox) and linking the model to views through it. However, study whatever controller carefully and choose it because of some capability it brings to the table that your application needs (caching is an example that comes to mind). Your views will likely need to be reimagined as well to interact with this new design, but what you should have is a system where the algorithms are now divorced from the UI, making the views' job easy. </p> <p>Realistically, the way you tackle this problem is iteratively. Find one system that can easily be teased out in the fashion I describe, get it under unit tests, validate with people as well, and continue to the next system. While a tedious process, I can assure it's much less work than trying to rewrite everything, which invites disaster unless you have a very good set of automated validation ahead of time. </p> <h1>Update</h1> <p>To reiterate, the tech is not going to solve your problem. Continued iteration toward more cohesive objects will. </p> <p>Now as far as coupled data, with an ORM you've made a tradeoff, and monolithic systems do have their benefits. Another approach would be giving one stateful entity a reference to another's service object via DI, such that you retrieve it through that. This would enable you to mock it for the purpose of unit testing and replace it with a similar service object and corresponding entity to facilitate reuse in other contexts. </p> <p>In terms of solving business problems (e.g. accounting) reuse is an emergent property where you write multiple systems that do roughly the same thing and then figure out how to generalize. Rarely if ever in my experience do you start out writing something to solve some business problem that becomes a reusable component. </p>
    singulars
    1. This table or related slice is empty.
    1. POCF Project getting too big, what shall one do?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USorangepips
    1. USorangepips
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCF Project getting too big, what shall one do?
      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. COI'm already using DDD w/ DI. However, I wonder which of those technologies I mention would give me a better organization of the pieces. The high level view suggests that they should be more loosely coupled, yet the reality is that the DB tables had to be coupled (e.g. FK to Staff.staff_id). Once coupled, it is harder to get out for reuse. Looking for a best of both world solution but doesn't seem like there's one.
      singulars
      1. PO
      1. USHenry
    2. CO@Henry: see my update.
      singulars
      1. PO
      1. USorangepips
 

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