Databases
StackOverflow2013
Postsdbo
POUsing nNHibernate with Emitted Code
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUsing nNHibernate with Emitted Code
    primarykey
    data
    text
    <p>I am developing a software that will serve as back-end for a data-ware house, in which fact definitions will be read from an xml file and corresponding fact/dimension tables will be created on the fly. </p> <p>I have managed to make it work i.e. the code creates tables, updates table structure if possible otherwise drop table and make an new one, it can insert data into tables and we can query data-ware house from our client application as well. So far so good.</p> <p>Now I have two problems</p> <p>1) Too many sql statements. The problem: it will be night mare to maintain</p> <p>2) Too many sql statements. The problem: I have been asked to support multiple databases that implies more sql statments.</p> <p>I have to admit that I have not worked much with either of (n)Hibernate or Reflection.Emit.</p> <p>But I was wondering how hard it would be to generate classes for my tables using Reflection.Emit and then use ActiveRecord/nHibernate to access data? So that I don't have to do the dirty work of dealing with a database directly.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USWPFAbsoluteNewBie
    1. USWPFAbsoluteNewBie
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUsing nNHibernate with Emitted Code
      1. This table or related slice is empty.
      1. VTUpMod
    1. COit would help to see the API of your backend. If all is queried by strings then considered writing fixed classes with an EAV-model.`class Fact { public virtual int Id { get; set; } /// <summary> /// Propertyname/Value pairs /// </summary> public virtual IDictionary<string, string> Properties { get; set; } }`
      singulars
      1. POUsing nNHibernate with Emitted Code
      1. USFiro
    2. COThe application interacts with clients using sockets. Clients can send in commands only two commands i.e. to update what fact we are collecting like "UPDATE_FACT_DEFINITIONS FACT_DEFINITION_XML_GOES_HERE" and query a fact i.e. "QUERY QUERY_DESCRIBED_IN_XML" After reading the fact definition file, we create appropriate fact and dimension tables and look for the desired facts in files under a known directory. The code knows the mapping between the file structure and facts. When a query is received, the code knows the tables to query, so it converts the xml to sql and returns the result.
      singulars
      1. POUsing nNHibernate with Emitted Code
      1. USWPFAbsoluteNewBie
    3. COI just looked into EAV-model. But it seems more complex to design. It not only would consume more space but also will be lot slower apparently which I dont want :(. More importantly I want to get rid of sql statements and I have found the following blog post regarding using this approach with nHibernate [link](http://bartreyserhove.blogspot.com/2008/02/dynamic-domain-mode-using-nhibernate.html) Can you point out a better starting point?
      singulars
      1. POUsing nNHibernate with Emitted Code
      1. USWPFAbsoluteNewBie
 

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