Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd prefer your "proxy" approach over other options, if I bothered with it at all.</p> <p>Truth of the matter is that I've found this to be such a major problem in ALL spheres of development that I tend to steer clear of using any library specific construct outside of my interaction with that particular library. One example might be in dealing with events/signals in various different libraries. I've already chosen boost as something that is <em>integral</em> to my own project code so I quite purposefully use boost::signals2 for all communication within my own project code. I then write interfaces to the UI library I'm using.</p> <p>Another example is strings. Every damn UI library out there reinvents the string. All of my model and data code uses the standard versions and I provide interfaces to my UI wrappers that work in such types...converting to the UI specific version only at that point where I'm interacting directly with a UI component.</p> <p>This does mean that I can't leverage a lot of power provided by the various independent but similar constructs, and I'm writing a lot of extra code to deal with these conversions, but it's well worth it because if I find better libraries and/or need to switch platforms it becomes MUCH easier to do so since I haven't allowed these things to weed their way throughout everything.</p> <p>So basically, I'd prefer the proxy approach because I'm already doing it. I work in abstract layers that distance me from any specific library I'm using and subclass those abstractions with the specifics required to interact with said library. I'm ALWAYS doing it, so wondering about some small area where I want to share information between two third party libraries is basically already answered.</p>
    singulars
    1. This table or related slice is empty.
    1. POLoosely coupled implicit conversion
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCrazy Eddie
    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. VTDownMod
    1. COIt actually sounds like (please correct me if I misunderstood!) you are working around the issue by wrapping other libraries with a thin layer of your own code. While that's totally fine, it just concentrates the glue-code in a module. However, that can be a lot of code for larger third party libraries! I'd actually like to get rid of as much glue-code as possible.
      singulars
      1. PO
      1. USltjax
    2. CO@ltjax If you're using third party libraries, almost by definition you don't have control over the API and will be required to use some sort of glue code to get the data back into a normalized form for use by your application. Consolidating the glue in one area makes it easier to maintain.
      singulars
      1. PO
      1. USMark B
    3. CO@Mark B: Yea, that's very true. But I don't see how it relates to my question, or my comment. I agree that having all the glue in one area makes it easier to maintain, but less code is also easier to maintain than a lot of code (given similar levels of complexity). You can have both with those approaches (unless I missed something, which is why I'm asking), while writing a wrapper module is just working around the problem, but is a lot less flexible and a lot more code.
      singulars
      1. PO
      1. USltjax
 

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