Features support

From http://drupalcode.org/project/features.git/blob/HEAD:/API.txt:

138 - Using a custom table with a serial ID for identifying configuration objects.
139 If this is the case, you will need to change your schema to use a string
140 identifier / machine name for each object.
141
142 **Features integration:** Fix your schema first, then see below.

Suggestion:
private_files_download_permission_directory: Throw 'did' column out, let 'path' be the primary key.
(One cannot duplicate a path on the UI anyway.)

private_files_download_permission_directory_user:
- Throw 'did' column out, introduce 'path' instead
- Instead of a serial 'duid' we could use a varchar 'duid' created from 'path' + 'uid'

private_files_download_permission_directory_role:
The same as private_files_download_permission_directory_user but instead of 'uid' and 'duid' we have 'rid' and 'drid'.

An uglier but (especially considering upgrade paths) simpler-to-implement solution would be just to add a varchar machine_name column to private_files_download_permission_directory_user and private_files_download_permission_directory_role.

Thoughts? Any chance on this being commited in case of a patch?

With Features you can export your configuration into code. This makes development of a site much easier. For example, on code you can use git, while on settings in a db you cannot.