Jump to content

Search the Community

Showing results for tags 'mysql'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Unreal Engine
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion
  • PlasticX Early Adopter Program's General Feedback
  • PlasticX Early Adopter Program's Issue Reporting
  • PlasticX Early Adopter Program's Feature Requests
  • PlasticX Early Adopter Program's Announcements

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. Hi, I`m Byungwook Choi. I am using PSCM(Version PlasticSCM- and DB(Mysql 5.5.39). I will now proceed with the PSCM Upgrade(Version PlasticSCM- Is there anything I need to consider to proceed with the PSCM Upgrade? ( something like Mysql Version, ...) I Would appreciate your kind attention. The information below is server information * Spec mysql Version = 14.14 Distrib 5.5.39, for Win64 (X86) OS = Windows Server 2008 R2 Standard Ram = 16GB Thanks, Byungwook Choi
  2. If you ever face the following error: --------------------------- Error --------------------------- There has been an unexpected error "Cannot execute statement: impossible to write to binary log since BINLOG_FORMAT = STATEMENT and at least one table uses a storage engine limited to row-based logging. InnoDB is limited to row-logging when transaction isolation level is READ COMMITTED or READ UNCOMMITTED.". For more information check the server log. --------------------------- OK --------------------------- is because MySQL is not liking the default Plastic isolation level. You can change it by adding the following entry in your "db.conf" server config file: <IsolationLevel>RepeatableRead</IsolationLevel> "RepeteableRead" is OK, no issues are reported so far using it, this is the first one you will want to try if you face the error described above. If it doesn't work... contact us!
  • Create New...