[RFC|Merged] Extensions

[brunoais]

You should change those names. Besides that, I agree with your proposal

[igorw]

Explain what you mean by keeping track of how many times an extension has been enabled. We have both migrations and the state column to keep track of state transitions.

[MichaelC]

Explain what you mean by keeping track of how many times an extension has been enabled. We have both migrations and the state column to keep track of state transitions.

In migrations, will it keep track of whether it has been installed previously and then purging would remove it?

[igorw]

Nils should correct me if I'm wrong, but I believe this to be the case.

[MichaelC]

After talking on IRC with naderman and igor:

There isn't an ext_id as it wouldn't really provide any benefits and name is required to be in the DB and unique anyway.

However, the name should be primary key so it is clear from looking at the schema which column is used for lookups.
So seeing as there isn't a problem with having strings as a primary key, it should be the primary key.

[DavidIQ]

You mean the name of the extension? How are you going to ensure it's unique? Maybe an additional identifier should be used like the permalink.

[MichaelC]

You mean the name of the extension? How are you going to ensure it's unique? Maybe an additional identifier should be used like the permalink.

Yes, the clean name of the extension that is in the directory and manifest (Human Name is also in the Manifest).
The unique constraint and the primary key would make it so it has to be unique too.
Permalink to what? Why would it need a permalink as the link is always the extension directory followed by the extension name...

[DavidIQ]

You mean the name of the extension? How are you going to ensure it's unique? Maybe an additional identifier should be used like the permalink.

Yes, the clean name of the extension that is in the directory and manifest (Human Name is also in the Manifest).
The unique constraint and the primary key would make it so it has to be unique too.
Permalink to what? Why would it need a permalink as the link is always the extension directory followed by the extension name...

I'm talking about where the extension repo will be at. You need to think about the correlation between what's installed and what is available for installation in the repo, wherever it may be.

[callumacrae]

You mean the name of the extension? How are you going to ensure it's unique? Maybe an additional identifier should be used like the permalink.

Hash!

[brunoais]

You mean the name of the extension? How are you going to ensure it's unique? Maybe an additional identifier should be used like the permalink.

Hash!

DB UNIQUE constraint.