Can not add Different **Monastery Swiftspear**

[Roker2]

Description

I did import from my list

4 Chain Lightning (BBD) 171
4 Curse of the Pierced Heart (ISD) 138
4 Fireblast (VIS) 79
2 Forgotten Cave (MH1) 239
3 Lava Spike (MMA) 121
1 Lava Spike (TSR) 347
4 Lightning Bolt (M10) 146
3 Monastery Swiftspear (KTK) 118
1 Monastery Swiftspear (PLST) IMA-140
1 Mountain (GK1) 101
3 Mountain (GK1) 49
1 Mountain (KLD) 259
1 Mountain (SOI) 294
1 Mountain (SOI) 293
1 Mountain (9ED) 345
1 Mountain (GK2) 79
1 Mountain (C19) 298
1 Mountain (VOW) 274
1 Mountain (VOW) 275
1 Mountain (DMR) 409
1 Mountain (MOM) 280
1 Mountain (MOM) 289
4 Needle Drop (LRW) 186
4 Rift Bolt (TSR) 184
1 Searing Blaze (DDI) 67
2 Searing Blaze (WWK) 90
4 Skewer the Critics (RNA) 115
4 Thermo-Alchemist (EMN) 147

And I don't see 3 Monastery Swiftspear from KTK. Also I tried to do it manually via Add cart, it was not added.

Searing Blaze is okay for example. Also I imported different Mountain cards. Maybe some cards can be imported, some - not. The list contains 60 cards, I see only 28 entries.

Steps to reproduce

1. Import the list
2. Try to add 3 Monastery Swiftspear via import or Add cart
   3 Monastery Swiftspear (KTK) 118

Expected behavior

I see 1 Monastery Swiftspear (PLST) IMA-140 and 3 3 Monastery Swiftspear (KTK) 118.

Actual behavior

I see only 1 Monastery Swiftspear (PLST) IMA-140

Environment

• OpenMTG version: 1.9.2
• Deployment: Docker image
• Configuration:

  openmtg:
    container_name: openmtg
    build: .
    image: ghcr.io/dredbaron/openmtg:latest
    restart: unless-stopped
    ports:
      - "8080:80"
    environment:
      DATABASE_URL: sqlite:////data/db/openmtg.db
      JWT_SECRET: he_he_I_will_not_show_it
      CONFIG_PATH: /config
      UPLOADS_PATH: /data/uploads
    volumes:
      - ./openmtg/config:/config
      - ./openmtg/uploads:/data/uploads
      - ./openmtg/trades:/data/trades
      - ./openmtg/sqlite-data:/data/db

Logs

No any logs :/ I don't see any errors

[DredBaron]

Issue is not reproducible on a PostgreSQL instance running version 1.9.2. Additional SQLite incompatibilities are suspected at this time, the issue is under investigation.

Until a patch release is issued and a full database audit is complete, I suggest all new instances use PostgreSQL. JSON imports will be created to allow for cross-database migrations.

[DredBaron]

Following up on this: the issue is still not reproducible on either a PostgreSQL or a SQLite instance. Both the bulk import and Add Card correctly created two separate entries for KTK 118 and PLST IMA-140 when testing the full list against both backends. Given that, I'm walking back the earlier recommendation to avoid SQLite as there's no evidence this is a database-layer problem specific to either backend. The current working theory is an as-yet-unidentified edge case, which will take more investigation to isolate.

A couple of things that would help narrow this down:

1. Completely restart the Docker container.
2. Retry the import while monitoring the Docker log.
3. Try adding Monastery Swiftspear in the different name formats to see if the format is the cause:
   • Adding it directly via card search / Add Card instead of the bulk importer
   • 3 Monastery Swiftspear (KTK) 118
   • 1x Monastery Swiftspear

If either of those still fails, please update this issue with exactly which one, and the investigation will continue. Until then, this issue will be left open, marked as investigating, and pinned.

Additionally, the "28 imported" count reflects unique cards, not total copies. Bulk importing 100 Chain Lightning (BBD) 171 would report "1 imported," since only one distinct line was processed.