packages vs package_versions (nuget)

[joonhwan]

I deployed af in my linux server using docker compose approach.
When i push 2 different versions of a same nuget package, 2 pacakges was created.
I expected that 1 package with 2 versions.

Is this by design ?

btw, what is the version of package (HERE mark) ?

  CREATE TABLE packages (
      id UUID PRIMARY KEY,
      repository_id UUID,
      name VARCHAR(255),
      version VARCHAR(100),     -- ← HERE 
      -- ...
      UNIQUE(repository_id, name, version)   
  );

  CREATE TABLE package_versions (
      id UUID PRIMARY KEY,
      package_id UUID REFERENCES packages(id),
      version VARCHAR(100),     
      -- ...
      UNIQUE(package_id, version)
  );

[brandonrc]

Not a misconfiguration on your side. At the storage layer each (repository, name, version) is its own row, that is the uniqueness key, so two versions of the same package are two rows. The intent is that listing and the UI group those rows by package name and show the versions underneath, rather than treating each version as a separate package.

The version column you marked is the version of that specific row, so for the NuGet case it is populated per published version.

Can you tell me where you're seeing "2 packages" rather than one package with two versions: the web UI package list, the NuGet index.json service, or a direct SQL query? If it's the UI or the NuGet service index showing them as separate packages, that's a grouping bug I'd want to fix, and I'll open an issue for it.