Create database design with requirement I has a small database structure with an Account and Person. I want apply the following requirement: 

Account have one Person

Person do not have necessarily one Account (can be null)

When I delete an Account I don't necessarily delete Person

When I delete a Person I want delete Account

How to do that ? (one to one relationship ? on delete cascade ?)

This is good ?



Some clarification after getting some answers:

Thank for your answers.
I try to explain more the contextual meaning of Account and Person.

A Person is a contact with personal profile (Physical person, Customer, Company).

An Account is specified by an username, password, email. It's really an account for sign in on a app.

Therefore a Person can be exist without a account. A Person can only have a maximum of 1 Account. In a other direction Account have necessarily a Person.

Consequently when we remove an Account the Person is not also remove. But When I remove Person this associated Account no longer needed.

PS: I use PostgreSQL.
An Account belongsTo a Person. A person can exist without an account.

If a Person hasOne Account, then Account's primary key should also be a foreign key to People.

create table people (
  person_id int primary key,
  meta1 text, 
  meta2 text
);

create table accounts (
  person_id int primary key references people(person_id) on delete cascade,
  meta1 text
);