MySQL Configuration for Altium DBLib and Parts

Link to MySQL Community Downloads

Video Link https://youtu.be/W-L1IPFr2Fc

Recommended Download: MySQL Installer for Windows

Recommended Configuration for Altium DBLIB and Parts.

MySQL Server Version 8.0.36
MySQL Workbench Version 8.0.36
MySQL Connector/ODBC Version 8.0.32

Notes:

Connector/ODBC Version 8.0.32 is Highly Recommended for use with Parts.

Connector/ODBC Version 8.0.33 and higher are NOT Recommended for use with Parts.

Click on the Archives Tab and look for MySQL Connector/ODBC Version 8.0.32

In Altium . . . Create a New DBLib ! ! !

Open Altium > File > New > Library > Database > Create

Select Use Connection String

Enter Connection String

Advanced >  Enter tick marks > Ok

Connect

There is a bug in Altium . . .  if you edit an existing DBLIB the connection it may fail. 

Example Error msg in Altium DBLIB . . . 

Could not get column list for table . . . 

If the Altium DBLib connection to the server fails then try creating a new DBLIB.

That's it !

Parts A365 Git Repo for Access DBLib

Please note the following Access database example is not for multiple remote librarians.

This solution is suitable where there is one librarian and multiple users.

A cloud hosted MySQL database can be used to support multiple remote users.

Create a folder and copy the following folders and files

Open Parts Repo.PrjPcb in Altium then right click

Select Make Project Available Online

Close the project in Altium

Use TortoiseGit to Add, Commit and Push files to the Parts Repo.

TortoiseGit can be used to commit and pull symbols and footprints from the repo.

That's it !

git: 'credential-manager-core' is not a git command.

Solution:

Open .gitconfig and delete two lines then save .gitconfig

[credential]

    helper = manager-core

C:\Users\UserName\.gitconfig

That's it !

Best Schematic and Library Practices

Problem:

Do NOT allowing swapping symbol pin locations in the schematic.  If you update from library later, it will use the symbol from the library that does not have swapped pin locations. 

Solution: Create an Alternate part in the *.Schlib

Problem:

When using DBLIBs do NOT leave Footprint Refs embedded in Schlib files or you can end up with the  wrong Footprint placed in the design.

Library Hierarchy is Left to Right and Top Down

I recommend you do NOT use the Search paths, or use them very wisely.

Altium will search your entire C: Drive you set the Search Path to C:\ 

Problem:

Duplicate Library or Footprint Ref.

Solution:

Use single part libraries with file names that match the Ref, then place all Symbols in a folder named Symbols.  Do the same for the Footprints, use single part PCBLIBs with matched Ref and File names placed in the Footprints folder.

If the Refs match the file names it will now be impossible to create a duplicate part using the same name when all of the like type libraries are in the same folder.

Note there should be no Footprints listed in the SCHLIB files.

I prefer using DBLIBs.

Problem:

Inconsistent file paths found in Footprint properties

Example two different users placing parts from the same DBLib

Solution:

Example

Use Version Controlled GIT Repo and instruct all users to Clone to the same Folder on their local machine, example  C:\Parts Git Repo

Folders in C:\Parts Git Repo\

Using Store Path Relative to Database Library' in the DBLIB will make your database portable. You can move the DBLib and libraries to another drive or folder with no need to specify the absolute path to the database.

As shown above the Symbols and Footprints folders should be in the same folder as the DBLib.