nhibernate - Do you think of the database or objects first when building applications? -


When you think of building an application, ask for the web, and it uses a relational database Is that what you think of the database before and then you should put the app in front of a front end or think about your programs and objects and how a database can store them. I am trying to change the way I think, but it has not been clicked (I'm not sure I am right in my evaluation too.)

I have other Hibernate and N Hibernate The questions are asked but I'm trying to nail it down. I think of applications with databases before database database and then think about the application. After hibernation, it seems that the use of hibernation seems different in a different way. They think about objects and classes. They are my exact opposite.

And in reference to being in hibernation. If I first think about the database, then does it start when there is a "bad" or "wrong" mentality? I am only able to find hibernate or other ORM - performance, database identification to find some consistent causes, and it is different from there. I want to use Hibernate but I want to contact it correctly It seems that there is a different way of completely selecting more databases than just display.

related:

.

You will obviously get a very different answer to this question, Think about it first, and then based on that object. I think it is easy for my brain to work this way, because I can see the database schema (and this is also very easy to show the relation between the database schema). @DDPI is okay here: you should design on the basis of the problem domain - which translates to thinking in the database for me, but it is different for different people.

The relations between the objects are not always clear, and therefore it is difficult to attract pictures that show their relationships to get objects from each other (but possibly a single table on the DB side) Using) can make things even more confusing, he said, in some complex applications, I have done both at the same time - for example, creating tables, as well as the object structure Building where many objects are obtained from the same base, and all use the same table

DB-Another argument for the first and the most ORM layer generates items based on the database schema So, if you design objects, then try to reverse the database engineer, then generate the orram object, you are doing things backwards and almost certainly You are not going to end up with the way you are designed on the papers before.

If you are using ORM which creates a database based on objects for you, then it is possible to do this in another way, and design your objects for the first time when Until you are modeling the problem domain correctly, it is less important if you are already creating databases or objects.


Everyone said, this is when I'm designing front-end side of the application, I design it with a pencil and paper, and backend (objects, databases, Or anything), think about how the data is stored. I just design the interface how do I want to see it and work?

The next thing is that the UI has a wire for the backend schema, which is sometimes very simple, and sometimes It's not so easy - but I've found out how it makes the best UI. Often I do not expose all the functionality, or only allow to configure simple settings (for example, only allow permissions to be applied, even if the backend is denied to be inherited in order to permit it). This means that your UI is not very complex, or at least it is easy to make the first version, but you do not want to make a limited backend in the future or change it a lot.

When you create a UI based on how the data is stored, or objects created by you, it looks exactly the same - a user who was designed by a programmer.


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -