Skip to content
This repository has been archived by the owner on Jul 5, 2024. It is now read-only.

Feature Request: Database #40

Open
VishwaJay opened this issue Aug 4, 2023 · 0 comments
Open

Feature Request: Database #40

VishwaJay opened this issue Aug 4, 2023 · 0 comments

Comments

@VishwaJay
Copy link

For my favorite VS Code icon pack, I'd like to see some handling for these added (for my own purposes, and what instigated the request):

  • text.sql - Any/all SQL scripts of any kind (MySQL, MariaDB, Postgre, SQLite, others)
  • sqlite.3.db - SQLite database (though occasionally binary for something else, it is correctly SQLite, as other packages are either out of production or have deprecated this extension)
    • sqlite.sqlite - Alternate for SQLite databases (deprecated, but LOTS of people still use this, so an icon is useful)

And then here are some that might be useful to the world (I tried to alphabetize this as I could):

  • autocad.acad - AutoCAD database
  • access.accdb - Please don't. Just don't. (M$ Access ... fine, if you must)
    • access.accdc - Access database, digitally signed
    • access.accdr - Access database, runtime mode
    • access.accdu - Access database wizard
    • access.accft - Access database template
    • Older, but not yet fully gone:
      • access.mdb - Access DB
      • access.mde - Access application (executable database)
      • access.mdt - Access database template
  • text.csv - Technically not a database, but very useful for data interchange and sometimes used as such.
  • dbase.dbf - old dBase files (still used, amazingly)
  • filemaker.fmp12 - Filemaker Pro database
  • filemaker.fmpsl - Filemaker Pro database snapshop
  • bin.inx - Database index file used by multiple apps
  • bin.kdb - Encrypted database (usually for things like Keepass but also for a few kinds of passworded SQL in several apps)
  • open.office.odb - OpenOffice open database (Apache's answer to Access, OpenDocument format)
  • vstudio.ncp - M$ C++ program database

Lots of icons already exist for these. But you have a history of making them far more understandable (i.e., legible) inside of a project.

I hope any of this is helpful!

Thanks in advance for any/all of these that you do. The collection is already pretty amazing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant