-
|
How to use it with an existing database? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
|
I need to make assumptions when you say database given the lack of detail in the question here. If you actually mean a database then you can use the connection string for the db like you normally would. Add a custom schema if you want to keep things isolated. If you mean an existing project, generally craftsman will be used most successfully with a scaffolded wrapt project. If you have some recognizable paths it might be able to scaffold out some stuff for you, but idk if that'll be worth all the reconciliation time. In the future, more detail than a single sentence would be helpful so I can give a better response. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply. I mean if I've already a database with its schema and tables + data. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah it's not really meant for that kind of use case. Another option could be to make a new Wrapt project with craftsman and do a db first migration, move the entities to a distinct folder, incrementally move to code first entities from craftsman. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe a feature to introduce. |
Beta Was this translation helpful? Give feedback.
-
|
Like I mentioned, depending on your situation, you should be able to do something along the lines of doing db first in an empty project. That will give you simple anemic entities and then you incrementally transition to craftsman scaffolded entities over time. Practically you'll have a lot of business logic in an existing project though so pulling over the db repetition is just a small part of the picture and probably won't be enough. That's a big reason this isn't an existing feature. Every project is different and wouldn't have a seamless plug and play transition |
Beta Was this translation helpful? Give feedback.
-
|
No. Today I've an old WebApi business logic that "talks" with the db. I wish to migrate on a new architecture. I can to what you said and then "copy" data from one db to another or change the connection. I'll try and I'll update you which solution I'll use. |
Beta Was this translation helpful? Give feedback.
Like I mentioned, depending on your situation, you should be able to do something along the lines of doing db first in an empty project. That will give you simple anemic entities and then you incrementally transition to craftsman scaffolded entities over time.
Practically you'll have a lot of business logic in an existing project though so pulling over the db repetition is just a small part of the picture and probably won't be enough.
That's a big reason this isn't an existing feature. Every project is different and wouldn't have a seamless plug and play transition