Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Assuming I'm understanding your question what you might want is a helper class for each entity you have with things like column names, property names and other useful things, especially if you want to use ICriteria searches. <a href="http://nhforge.org/wikis/general/open-source-project-ecosystem.aspx" rel="nofollow noreferrer">http://nhforge.org/wikis/general/open-source-project-ecosystem.aspx</a> has plenty of projects that might help. NhGen (<a href="http://sourceforge.net/projects/nhgen/" rel="nofollow noreferrer">http://sourceforge.net/projects/nhgen/</a>) creates very simple helper classes which might help point you down a design path for what you might want.</p> <p><strong>Clarification Edit:</strong> following an "I don't understand" comment</p> <p>In short, I don't beleive there is a solution for you just yet. The QueryOver project hasn't made it as far as you want it to. So as a possible solution in the mean time, to remove magic strings build a helper class, so your query becomes</p> <pre><code>var x = session.QueryOver&lt;Shuttle&gt;().Add(SpatialRestrictions.Intersects(ShuttleHelper.Abc, other_object)); </code></pre> <p>That way your magic string is behind some other property ( I just chose .Abc to demonstrate but I'm sure you'll have a better idea of what you want ) then if "abc" changes ( say to "xyz" ) you either change the property name from .Abc to .Xyz and then you will have build errors to show you where you need to update your code ( much like you would with lambda expressions ) or just change the value of the .Abc property to "xyz" - which would really only work if your property had some meaningfull name ( such as .OtherObjectIntersectingColumn etc ) not that property name itself. That does have the advantage of not having to update code to correct the build errors. At that point your query could be</p> <pre><code>var x = session.QueryOver&lt;Shuttle&gt;().Add(SpatialRestrictions.Intersects(ShuttleHelper.OtherObjectIntersectingColumn, other_object)); </code></pre> <p>I mentioned the open source project ecosystem page as it can give you some pointers on what types of helper classes other people have made so your not re-inventing the wheel so to speak.</p>
    singulars
    1. This table or related slice is empty.
    1. POGetting magic strings out of QueryOver (or Fluent NHibernate perhaps)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. UScdmdotnet
    1. UScdmdotnet
    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. This table or related slice is empty.
    1. COI don't really understand your answer... sorry.
      singulars
      1. PO
      1. USDavid Pfeffer
    2. COThe answer has been edited as I couldn't clarify it for you in a comment
      singulars
      1. PO
      1. UScdmdotnet
    3. CO-1er. Could you please explain your downvote?
      singulars
      1. PO
      1. USDavid Neale
 

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