1

Topic: All the same Id or ObjectId

Earlier considered what well to have in tables and classes ObjectId a key as everywhere it is obvious with what you work. Now I look that in  repositories to have simply Id more conveniently to make Crud for all at once and not to write the  for each table. What tell?

2

Re: All the same Id or ObjectId

Hello, snaphold, you wrote: S> considered what well to have in tables and classes ObjectId key S> Earlier as everywhere it is obvious with what you work. S> now I look that in  repositories to have simply Id more conveniently to make Crud for all at once and not to write the  for each table. S> that tell? If speech about a column title, always I name id. If select under the several tables, all links to fields I specify a table title, it turns out conveniently and readably.

3

Re: All the same Id or ObjectId

Hello, snaphold, you wrote: S> considered what well to have in tables and classes ObjectId key S> Earlier as everywhere it is obvious with what you work. S> now I look that in  repositories to have simply Id more conveniently to make Crud for all at once and not to write the  for each table. S> that tell? Heard judgement that like it would be desirable to name EntityId for convenience. Though problems with Id I do not see.

4

Re: All the same Id or ObjectId

Hello, snaphold, you wrote: S> considered what well to have in tables and classes ObjectId key S> Earlier as everywhere it is obvious with what you work. S> now I look that in  repositories to have simply Id more conveniently to make Crud for all at once and not to write the  for each table. S> that tell? It not repositories, is gateways of tabular data which are not necessary because already is ready ORM which you you use (therefore you under tables you imply data structures from your code). The gateway hides operation with bare SQL - but at you it and so it is hidden ORM. Means, you are free to use names of type ObjectId still.