I 'm using PowerDesigner 16.1 to create cdm and pdm models, and Bigazi to create Business Procees models, I want to exchange data and models between both of it. So I need a file format that is supported by the two tools
Related
I like to use the EntityFramework for persistence of the IndentityServer4 configuration data. But I was wondering why the same model Classes are duplicated in Model / Entities? Are both models always kept in sync? If I use the Entities, can I still include the Models project to use some convenient const and enum classes which are available in Models but not in Entities? Or is it better when using Entities to not include the Models library to prevent confusion.
Please advice.
The Models are duplicated in the IdentityServer4.EntityFramework library so that the models can be mapped to entities that make sense to Entity Framework (see the many lists of strings that need to be turned into entities so that they can be stored in separate tables). These entities are kept in sync by the IdentityServer team and the community.
There are mapper extensions for both types to convert them into one another: ToModel() and ToEntity().
Always use the Models unless you are communicating directly with the database.
When modeling a CouchDB object in Backbone, should there be a 1-1 relationship between a backbone model and a CouchDB database?
Currently, my models are around database documents and not a whole database. I am also using PouchDB to communicate witch CouchDB.
CouchDB dev here. Would not make them match 1:1. put all docs that belong to an app into a single database and give them a type field. Use a view to get all docs per type (or put the type as the prefix of the _id and use _all_docs/allDocs()) and have all docs of a type match the backbone model 1:1).
After a bunch of research and experimentation I came to the following conclusions.
You should use collections to model your database if your database holds related documents OR if you are using PouchDB.
Here is why:
1) A collection that holds related models is analogous to a a database that holds related documents.
2) Most importantly, if you are using PouchDB, you should use a collection to model your database. By doing so you can tie a collection to a PouchDB object and take advantage of backbone's events when the database or collection changes.
The alternative is to pass a reference to a PouchDB instance to each model.
I'm Developing a website using asp.net and sql server i'm using EF with the code first approach as a Data access layer, and the business logic layer(BLL) i've developed a class for each entity that contains functions to query the data base and return object of this entity, my question is about the where i can implement functions that returns data from different tables not from only one table in the BLL.
DAO layer is supposed to create model objects from underlying datastore. In some cases, to create a particular model, different tables have to be queried. In this case, it will be the DAO that will interact with multiple tables (not the service).
BLL might deal with different models in the same service. However, it should depend on one DAO for one model.
In other words, DAOs are mapped to model classes not underlying tables.
I am new to Semantic Web and I have a very basic question about
the JENA RDF Dataset. I read it from the documentation that a dataset is
a collection of graphs (or Models in the Java API). If I view the graph
(the model) as a RDF Alternative to Relational DB's 'Table', can I view
the dataset as a 'Database' ?
If so, then with TDB I should be able to create multiple
datasets. However in the documentation it says 'Every dataset is
obtained via TDBFactory.createDataset(Location) within a JVM is the same
dataset.' (http://jena.apache.org/documentation/tdb/datasets.html). I
also recall that the documentation said somewhere that the TDB does not
support multiple JVM now. Does that mean with TDB I can create ONLY ONE
dataset?
This is Andy's answer to my question in the jena users mailing list. Thanks, Andy.
Hi, Everyone
I am new to Semantic Web and I have a very basic question about
the JENA RDF Dataset. I read it from the documentation that a dataset is
a collection of graphs (or Models in the Java API). If I view the graph
(the model) as a RDF Alternative to Relational DB's 'Table', can I view
the dataset as a 'Database' ?
yes - sort of.
If so, then with TDB I should be able to create multiple
datasets. However in the documentation it says 'Every dataset is
obtained via TDBFactory.createDataset(Location) within a JVM is the same
dataset.' (http://jena.apache.org/documentation/tdb/datasets.html).
... for the same "location" argument ...
TDBFactory.createDataset("DB1") ;
TDBFactory.createDataset("DB2") ;
are different datasets
I
also recall that the documentation said somewhere that the TDB does not
support multiple JVM now. Does that mean with TDB I can create ONLY ONE
dataset?
TDB is the core database engine, and when used directly, you are using
in a kind of embedded mode.
You can use Jena Fuseki for sharing a dataset between applications (just
like you might share an SQL database between apps, except it's HTTP not
JDBC).
Andy
I want to develop a generic CRM application using SQL Server 2008.
The application must enable custom user fields using some extension technique.
I read a lot about the different options such as:
Observable Pattern, and
Entity Attribute Value (EAV)
But unfortunately these options are difficult to implement and I understand the application performance is affected and also it's difficult to query the repository using Entity Framework Code First.
I would appreciate some other simple options to implement.
Most of the time a package extension system like this is used to add user-defined columns to existing tables.
You can allow users to define their own tables which are placed in their own (segregated) schema. Your administration UI which manages this extension process will need to run the DDL code necessary to build these user-defined tables. If they are defined as being an extension of a predefined table, your system should enforce a 1:1 relationship between the predefined and user-defined table that it extends. You could also allow free-standing user-defined tables, if you want.
Once you have your user-defined tables created, use a (predefined) mapping table to connect the user-defined tables/columns to your predefined fields in your CRM UI. If you also allow users to define UI forms and fields, then your mapping table can tie to these too/instead.