syntax = "proto2";                      // Indicates compliance with proto2 syntax specification
package myTcaplusTable;                 // Self-defined package name

import "tcaplusservice.optionv1.proto"; // This file defines some common information for Tcaplus tables and needs to be referenced (imported) in your table definition

message player {  // Use message to define the table, the message name is the table name

    // Only a message with the primary key option (tcaplusservice.tcaplus_primary_key) specified can be recognized as a TcaplusDB business data table; otherwise, this message is just a structure
    // The primary key option specifies the list of primary key field names, separated by commas, with up to four fields being specified as primary keys
    option(tcaplusservice.tcaplus_primary_key) = "uin,name,region";

    // The tcaplusservice.tcaplus_index option specifies Tcaplus indexes
    // Each index must include primary key fields, and the intersection of all index field sets must not be empty
    option(tcaplusservice.tcaplus_index) = "index_1(uin,region)";
    option(tcaplusservice.tcaplus_index) = "index_2(uin,name)";

    // option(tcaplusservice.tcaplus_sharding_key) = "uin"; Users can explicitly set the index sharding field. If not explicitly set by the user, the system will default to using the primary key fields as sharding fields

    option(tcaplusservice.tcaplus_field_cipher_suite) = "DefaultAesCipherSuite"; // Use the default DefaultAesCipherSuite encryption function, optional setting 
    option(tcaplusservice.tcaplus_cipher_md5)= "62fee3b53619b7f303c939964c6f2c4b"; // Set the MD5 value for the encrypted password string, optional setting

    // Next is the table's Field Definition
    // TcaplusDB table supports the following data types:
    // Non-nested Type: int32, int64, uint32, uint64, sint32, sint64, bool, fixed64, sfixed64, double, fixed32, sfixed32, float, string, bytes
    // Nested Type: message
    // Tcaplus supports REQUIRED, OPTIONAL and REPEATED as Field Modifiers

    // Primary Key Fields (up to 4)
    required int64 uin = 1; // Primary key fields must be marked as required and cannot be of nested type
    required string name = 2 [(tcaplusservice.tcaplus_crypto) = true]; // string and bytes fields in messages can be designated as encrypted fields, optional setting
    required int32 region = 3;
    // A table can contain up to 4 primary key fields

    // Ordinary Value Field
    required int32 gamesvrid = 4; // Ordinary fields can be marked as required, optional, or repeated
    optional int32 logintime = 5 [default = 1];
    repeated int64 lockid = 6 [packed = true]; // Fields marked as repeated need to have the packed=true option specified
    optional bool is_available = 7 [default = false]; // Optional fields can specify default values
    optional pay_info pay = 8; // The type of value field can be a self-defined structure type
}

message pay_info { // Using message definition structure

    required int64 pay_id = 1;
    optional uint64 total_money = 2;
    optional uint64 pay_times = 3;
    optional pay_auth_info auth = 4;

    message pay_auth_info { // Structure type supports nested definition
        required string pay_keys = 1;
        optional int64 update_time = 2;
    }
}

syntax = "proto3"; // Indicates compliance with the proto3 syntax specification
package myTcaplusTable;                 // Self-defined package name

import "tcaplusservice.optionv1.proto"; // This file defines some common information for Tcaplus tables and needs to be referenced (imported) in your table definition

message player {  // Use message to define the table, the message name is the table name

    // Only a message with the primary key option (tcaplusservice.tcaplus_primary_key) specified can be recognized as a TcaplusDB business data table; otherwise, this message is just a structure
    // The primary key option specifies the list of primary key field names, separated by commas, with up to four fields being specified as primary keys
    option(tcaplusservice.tcaplus_primary_key) = "uin,name,region";

    // The tcaplusservice.tcaplus_index option specifies Tcaplus indexes
    // Each index must include primary key fields, and the intersection of all index field sets must not be empty
    option(tcaplusservice.tcaplus_index) = "index_1(uin,region)";
    option(tcaplusservice.tcaplus_index) = "index_2(uin,name)";

    // option(tcaplusservice.tcaplus_sharding_key) = "uin"; Users can explicitly set the sharding field themselves. If the user does not explicitly set it, the system will default to using the primary key field as the sharding field

    option(tcaplusservice.tcaplus_field_cipher_suite) = "DefaultAesCipherSuite"; // Use the default DefaultAesCipherSuite encryption function, optional setting
    option(tcaplusservice.tcaplus_cipher_md5)= "62fee3b53619b7f303c939964c6f2c4b"; // Set the MD5 value for the encrypted password string, optional setting

    // Next is the table's Field Definition
    // TcaplusDB table supports the following data types:
    // Non-nested Type: int32, int64, uint32, uint64, sint32, sint64, bool, fixed64, sfixed64, double, fixed32, sfixed32, float, string, bytes
    // Nested Type: message

    // Primary Key Fields (up to 4)
    int64 uin = 1; // Primary key fields must be non-nested types
    string name = 2[(tcaplusservice.tcaplus_crypto) = true]; // String and bytes fields in messages can be designated as encrypted fields, optional setting
    int32 region = 3;
    // A table can contain up to 4 primary key fields

    // Ordinary Value Field
    int32 gamesvrid = 4;
    int32 logintime = 5;
    int64 lockid = 6;
    bool is_available = 7;
    pay_info pay = 8; // The type of value field can be a self-defined structure type
}

message pay_info { // Using message definition structure

    int64 pay_id = 1;
    uint64 total_money = 2;
    uint64 pay_times = 3;
    pay_auth_info auth = 4;

    message pay_auth_info { // Structure type supports nested definition
        string pay_keys = 1;
        int64 update_time = 2;
    }
}