MySQL to Protocol Buffers Converter

About MySQL to Protocol Buffers Converter

Convert MySQL database dumps (CREATE TABLE and INSERT statements) to Protocol Buffers (protobuf) schema and data format. Perfect for data serialization, API development, and microservices communication.

Key Features

• Automatic Type Detection: Infers field types (string, bool, int32, int64, double)
• Schema Generation: Creates proto3 syntax schema definitions
• Sample Data: Includes textproto format sample data (first 100 records)
• Field Sanitization: Converts MySQL column names to valid protobuf field names
• MySQL Parser: Accurately parses MySQL CREATE TABLE and INSERT syntax
• File Upload: Upload .sql files directly
• Copy & Download: Easy export as .proto file

How to Use

1. Input MySQL Data: Paste your MySQL CREATE TABLE and INSERT statements or upload a .sql file
2. Review Output: The Protocol Buffers schema and data generate automatically
3. Copy or Download: Use the Copy or Download button to save your .proto file

Type Detection

The converter automatically detects field types based on data values:

• bool: Values matching "true" or "false" (case-insensitive)
• int32: Integer values within -2,147,483,648 to 2,147,483,647
• int64: Integer values outside int32 range
• double: Floating-point numbers with decimal points or scientific notation
• string: All other values (default type)

Example Conversion

MySQL Input:

CREATE TABLE employees (
  id INT PRIMARY KEY,
  name VARCHAR(100),
  age INT,
  salary DECIMAL(10,2)
);

INSERT INTO employees VALUES (1, 'John Doe', 28, 75000.00);
INSERT INTO employees VALUES (2, 'Jane Smith', 34, 82000.50);

Protocol Buffers Output:

syntax = "proto3";

package mysql_converter;

message MySQLRecord {
  int32 id = 1; // id
  string name = 2; // name
  int32 age = 3; // age
  double salary = 4; // salary
}

message MySQLData {
  repeated MySQLRecord records = 1;
}

// Sample data in textproto format
MySQLData {
  records {
    id: 1
    name: "John Doe"
    age: 28
    salary: 75000.00
  }
  records {
    id: 2
    name: "Jane Smith"
    age: 34
    salary: 82000.50
  }
}

Common Use Cases

• API Development: Define data schemas for gRPC services
• Microservices: Create message formats for service communication
• Data Serialization: Efficient binary data encoding
• Cross-Platform: Language-agnostic data structures
• Database Migration: Convert MySQL schemas to protobuf format
• Data Archival: Archive MySQL data in efficient protobuf format

Protocol Buffers Benefits

• Compact: Binary format is smaller than JSON or XML
• Fast: Efficient serialization and deserialization
• Typed: Strong typing prevents data errors
• Versioned: Forward and backward compatibility
• Multi-Language: Code generation for 20+ languages
• Validated: Schema-based validation

Field Name Sanitization

MySQL column names are automatically converted to valid protobuf field names:

• Converts to lowercase with underscores
• Removes special characters and accents
• Ensures names start with letters
• Handles duplicate names with numeric suffixes
• Generates default names for empty headers

Supported MySQL Data Types

• Numeric: INT, BIGINT, DECIMAL, FLOAT, DOUBLE → int32/int64/double
• String: VARCHAR, CHAR, TEXT, MEDIUMTEXT, LONGTEXT → string
• Boolean: BOOLEAN, TINYINT(1) → bool
• NULL: NULL values are omitted from textproto output

Output Format

The converter generates three sections:

• Schema Definition: proto3 syntax with message types
• Statistics Comment: Number of rows processed
• Sample Data: First 100 records in textproto format

FAQ

• Do I need both CREATE TABLE and INSERT statements? The converter can infer columns from INSERT statements alone, but including CREATE TABLE helps produce clearer field names and more accurate typing.
• How are large integers handled? Values outside the 32-bit integer range are promoted to int64 to avoid overflow, while smaller integers are typed as int32.
• What happens with NULL values? NULL or empty values are omitted from the textproto sample, which is a common pattern for sparse data; you can add default values in your application schema if needed.
• Can I change message or package names? Yes. After generation, you can rename the MySQLRecord, MySQLData, and mysql_converter identifiers to match your project conventions.
• Is my data sent anywhere? No. Parsing and schema generation run entirely in your browser and do not send your SQL input to a backend.

Privacy & Security

All conversions happen locally in your browser. Your MySQL data is never uploaded to any server, ensuring complete privacy and security.