Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, you may well be better off biting the bullet and refactoring your code to reduce the impact of all of this customization. There are good patterns that allow for this type of scenario (configuration-driven, plugins, software factory come to mind).</p> <p>Having said that, if the application is as you describe (each client requires wide-reaching changes to the core), you may want to explore whether using compiler directives to isolate individual client changes works better for you than branching. The trouble with branching (as I'm sure you discovered) is that a fix placed in one branch often needs to be propagated to all other branches (since you never have the intention of merging the branches in the future). Additionally, you might need to fix the production version running at one client, while still developing on the next version for that client... a branch of a branch.</p> <p>Things will only get worse if you continue this branch-per-client strategy as you add new clients. </p>
    singulars
    1. This table or related slice is empty.
    1. POVersion control "best practice"
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USEric J.
    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. COyeah, but this is an "old" app (html/asp/vb6) and now it's impossible to refactor the "thing".. the change might be just a set of customized pages (like different images, or text labels or something "trivial"). How do i keep the standard version and this new version in the version control system?
      singulars
      1. PO
      1. USAntonio Dias
    2. COI was responsible for a very large app that was VB6 based, and was highly configurable. There's nothing about that technology that makes it impossible to refactor, though I do understand that you probably have a very large code base to deal with. You'll need to honestly evaluate whether the (high) cost of refactoring (focusing on areas where you have the most customization) is greater than the high cost of not refactoring. Only you know your app. Just be honest about the true cost of each alternative.
      singulars
      1. PO
      1. USEric J.
    3. COyeah, i know, but the cost to refactor is really high, not just in terms of the work needed but also because there's only two people maintaning the app, as there's new request coming all the time and a lot of bugs to fix. The app already allows a certain dgree of customization (mainly in the design) but my problem is if someone asks for a new "module" (a group of pages and some code) where do i keep these new pages in the VCS? Along with all the other standard pages? Do i create a new repository (project) just for these changes and to integrate i pull the core modules and "add" the new one?
      singulars
      1. PO
      1. USAntonio Dias
 

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