revert the renaming of virtual_users to virtual_mailboxes
It does not really add much value and makes things more complicated during migration. Plus the table contains passwords so it's more than just the mailboxes.
This commit is contained in:
parent
28edb36704
commit
6de9d4f6c7
5 changed files with 10 additions and 10 deletions
|
|
@ -83,7 +83,7 @@ By now you have an empty database and two user accounts to access it. Now you ne
|
|||
|
||||
- virtual_domains
|
||||
- virtual_aliases
|
||||
- virtual_mailboxes
|
||||
- virtual_users
|
||||
|
||||
Let's create the entire database schema in one go:
|
||||
|
||||
|
|
@ -107,7 +107,7 @@ CREATE TABLE IF NOT EXISTS `virtual_aliases` (
|
|||
FOREIGN KEY (domain_id) REFERENCES virtual_domains(id) ON DELETE CASCADE
|
||||
);
|
||||
|
||||
CREATE TABLE IF NOT EXISTS `virtual_mailboxes` (
|
||||
CREATE TABLE IF NOT EXISTS `virtual_users` (
|
||||
`id` int(11) NOT NULL auto_increment,
|
||||
`domain_id` int(11) NOT NULL,
|
||||
`email` varchar(100) NOT NULL,
|
||||
|
|
@ -138,7 +138,7 @@ represents a domain.
|
|||
|
||||
</Aside>
|
||||
|
||||
### virtual_mailboxes
|
||||
### virtual_users
|
||||
|
||||
The second table contains information about your users. Each mail account requires one row in this table.
|
||||
|
||||
|
|
@ -211,7 +211,7 @@ REPLACE INTO virtual_domains
|
|||
(id, name)
|
||||
VALUES (10,'example.org');
|
||||
|
||||
REPLACE INTO virtual_mailboxes
|
||||
REPLACE INTO virtual_users
|
||||
(id, domain_id, password, email)
|
||||
VALUES (
|
||||
1,
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue