It's recommended to use different database schemas for process runtime and logging due to performance reasons. Because of this the schemas are separated. Of course you can use single database for non-production purposes, but to use the relation that you describe, you need to add foreign key manually.
I was looking to query the database to get some task related information. But anyway I achieved that using TaskClient.
Still if we need a foreign key, we can add one manually, but is this recommended? I mean in a scenario where nothing is going your way and joining two tables is only thing you have left. Will this affect may be some thing in some way?
Or is it just that if you need it you can create one. No issues at all?
1 of 1 people found this helpful
As explained before the main reason is to be possible to separate logging database schema and runtime database schema. If each would be tied together using foreign keys, it would not be possible to split them easily. My opinion is that sometimes it's necessary to update database schema manually. For example some databases don't create indexes by default, you need to add them manually, if you need them. You have to try it in your scenario if foreign key adding won't damage anything. I think that it should not. FYI I am not a jBPM developer, so I cannot guarantee that
No Problem. Thanks man.