• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. PCB Design
  3. CIS connected to MySQL database

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 164
  • Views 16170
  • Members are here 0
More Content
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

CIS connected to MySQL database

stetag
stetag over 11 years ago

I tried to configure CIS to my Enterprise MySQL Database but Orcad return the follow error message:

ERROR(ORCIS-6233): The Table Property Type of the field PartNumber in table Resistors is not of type TEXT, STRING or CHARACTER. The Table Property Type of the field assigned as Property Type Part_Number has to be one of the above.

 

this is the structure of my table:

CREATE TABLE `Resistors` (

 `ID` int(10) unsigned NOT NULL,

  `PartNumber` text,

  `PArtType` varchar(255) DEFAULT NULL,

  `SchematicPart` varchar(255) DEFAULT NULL,

  `Value` varchar(255) NOT NULL,

  `Availability` varchar(255) DEFAULT NULL,

  `Data Sheet` varchar(255) DEFAULT NULL,

  `Description` varchar(255) DEFAULT NULL,

  `Manufacturer` varchar(255) DEFAULT NULL,

  `MftrNb` varchar(255) DEFAULT NULL,

  `PCBfootprint` varchar(255) DEFAULT NULL,

  PRIMARY KEY (`ID`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8; 

 

Can you help me?

Best regards

Stefano 

 

  • Cancel
  • oldmouldy
    oldmouldy over 11 years ago

    Set the Field Type to VARCHAR(<some number>) for all the fields in the database, they will be correctly recognised as "text" - this is down to the nuances of SQL and "Microsoft Jet" data sources. You might want to restrict some of the field sizes since many of these will never be 255. You probably want to have "PartNumber" as your primary key to avoid duplicates of PartNumber and associated issues.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stetag
    stetag over 11 years ago

    I canged the field to varchar and set as primary key the partNumber column, but still the error

     

    CREATE TABLE `Resistors` (

      `PartNumber` varchar(45) NOT NULL,

      `PArtType` varchar(45) DEFAULT NULL,

      `SchematicPart` varchar(45) DEFAULT NULL,

      `Value` varchar(100) DEFAULT NULL,

      `Availability` varchar(45) DEFAULT NULL,

      `Data Sheet` varchar(254) DEFAULT NULL,

      `Description` varchar(254) DEFAULT NULL,

      `Manufacturer` varchar(45) DEFAULT NULL,

      `MftrNb` varchar(45) DEFAULT NULL,

      `PCBfootprint` varchar(45) DEFAULT NULL,

      PRIMARY KEY (`PartNumber`) USING BTREE

    ) ENGINE=InnoDB DEFAULT CHARSET=utf8; 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • oldmouldy
    oldmouldy over 11 years ago

    I have no idea, this SQL works with MySQL to create a Resistor table for the default Bench database, specify the <database> name:

    USE <database>;

    DROP TABLE IF EXISTS Resistor;

    CREATE TABLE Resistor (
    PartNumber VARCHAR(50) NOT NULL PRIMARY KEY,
    Parttype VARCHAR(50),
    Value VARCHAR(50),
    Description VARCHAR(50),
    Power VARCHAR(50),
    Tolerance VARCHAR(50),
    SchematicPart VARCHAR(50),
    LayoutPCBFootprint VARCHAR(50),
    AllegroPCBFootprint VARCHAR(50),
    PSpice VARCHAR(50),
    ManufacturerPartNumber VARCHAR(50),
    Manufacturer VARCHAR(50),
    DistributorPartNumber VARCHAR(50),
    Distributor VARCHAR(50),
    Price DOUBLE,
    Availability VARCHAR(50),
    Datasheet VARCHAR(50),
    ActivepartsID VARCHAR(50)
    );

    Maybe you need to "drop" the current table before creation of the replacement? 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stetag
    stetag over 11 years ago

    **RESOLVED** 

    I found my problem,

    I need to use the "MySQL ODBC x.x ANSI Driver" and not the  "MySQL ODBC x.x Unicode Driver"

     

    Tanks you for your help! 

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information