Design database - is it the good approach ?

[jaryszek]

Hi,

I have relanships something like that:



Is it the good approach when you are creating the database ?

I have features and fields (for example dates) which will be characteristic only for one document (tbl_pelnomocnictwa mirrors one document).



I could place these separately fields in separately tables within one summary table (tbl_Pelnomocnictwa) but there is a lot of fields so i changed it for 3 tables in order to delete fields from my summary table () and to not do my summary table very big.

What do you think?
Better do only one 1to1 relanthip or it doesnt matter what is their number in relational database?

Thank you for your tips,
Best Wishes,
Jacek Antek

[ranman256]

I also use some 1:1 tables for some cases. It works.

[jaryszek]

But you have to often build form with inconsistent data type in order to input data...

Thank you!

[aytee111]

Not sure what you mean by "summary" table. Do not use tables to store calculated fields, have standard queries for this instead.

[ssanfu]

IMHO, it is a bad idea, unless you are doing something like keeping salaries from being see by everyone.

If 1 to 1, then the fields should be in the same table.

there is a lot of fields

How many are "a lot of fields"???

[jaryszek]

Thank you Guys!

In tbl_Pelnomocnictwa as you can see there is about 15 fields.

Summary table is 1 to 1 relationship table where user input new ticket.
One record = one new ticket

Best wishes,
Jacek Antek

[jaryszek]

Sometimes i think that it is no inevitable to avoid 1to1 relationshiop,

please look below:



tbl_Spolki is automatically updated from Excel file via macro.
So i can not add foreign key here and make this table as many relationship.

So only what i can do it is create foreing key in table tbl_Pel_osoba so 1to1 relationship is inevitable here.

Best wishes,
Jacek Antek

[jaryszek]

up,

Jacek Antek

[June7]

I also have one db where 1-to-1 related tables were preferred.

It is a balancing act between normalization and ease of data entry/edit. "Normalize until it hurts, denormalize until it works."

However, I am not convinced that tbl_Pelnomocnictwa and tbl_Daty_wniosku really need to be separate.

[jaryszek]

Thank you June7,

I think that is not necessary also but is looking prettier

Best Wishes,
Jacek Antek