from peewee import * # SQLite database using WAL journal mode and 64MB cache. sqlite_db = SqliteDatabase('/path/to/app.db', pragmas={ 'journal_mode': 'wal', 'cache_size': -1024 * 64}) # Connect to th/to/app.db', regexp_function=True, timeout=3, pragmas={'journal_mode': 'wal'}) from playhouse.postgres_ext import PostgresqlExtDatabase # Use Postgres (and register hstore extension) org/2/library/sqlite3.html#sqlite3.connect]. sqlite_db = SqliteDatabase('my_app.db', pragmas={'journal_mode': 'wal'}) class BaseModel(Model): """A base model that will use our Sqlite database.""" class Meta:

from peewee import * # SQLite database using WAL journal mode and 64MB cache. sqlite_db = SqliteDatabase('/path/to/app.db', pragmas={ 'journal_mode': 'wal', 'cache_size': -1024 * 64}) # Connect to th/to/app.db', regexp_function=True, timeout=3, pragmas={'journal_mode': 'wal'}) from playhouse.postgres_ext import PostgresqlExtDatabase # Use Postgres (and register hstore extension) org/2/library/sqlite3.html#sqlite3.connect]. sqlite_db = SqliteDatabase('my_app.db', pragmas={'journal_mode': 'wal'}) class BaseModel(Model): """A base model that will use our Sqlite database.""" class Meta:

from peewee import * # SQLite database using WAL journal mode and 64MB cache. sqlite_db = SqliteDatabase('/path/to/app.db', pragmas=( ('journal_mode', 'wal'), ('cache_size', -1024 * 64))) # Connect h/to/app.db', regexp_function=True, timeout=3, pragmas=(('journal_mode', 'wal'),)) from playhouse.postgres_ext import PostgresqlExtDatabase # Use Postgres (and register hstore playhouse.sqlite_ext import SqliteExtDatabase sqlite_db = SqliteExtDatabase('my_app.db', journal_mode='WAL') PRAGMA statements SQLite allows run-time configuration of a number of parameters through PRAGMA

from peewee import * # SQLite database using WAL journal mode and 64MB cache. sqlite_db = SqliteDatabase('/path/to/app.db', pragmas=( ('journal_mode', 'wal'), ('cache_size', -1024 * 64))) # Connect h/to/app.db', regexp_function=True, timeout=3, pragmas=(('journal_mode', 'wal'),)) from playhouse.postgres_ext import PostgresqlExtDatabase # Use Postgres (and register hstore playhouse.sqlite_ext import SqliteExtDatabase sqlite_db = SqliteExtDatabase('my_app.db', journal_mode='WAL') PRAGMA statements SQLite allows run-time configuration of a number of parameters through PRAGMA

from peewee import * # SQLite database using WAL journal mode and 64MB cache. sqlite_db = SqliteDatabase('/path/to/app.db', pragmas=( ('journal_mode', 'wal'), ('cache_size', -1024 * 64))) # Connect h/to/app.db', regexp_function=True, timeout=3, pragmas=(('journal_mode', 'wal'),)) from playhouse.postgres_ext import PostgresqlExtDatabase # Use Postgres (and register hstore playhouse.sqlite_ext import SqliteExtDatabase sqlite_db = SqliteExtDatabase('my_app.db', journal_mode='WAL') PRAGMA statements SQLite allows run-time configuration of a number of parameters through PRAGMA

use the schema migrations extension to alter your database schema using Python. Note You can also write database.create_tables([User, ...], True) and peewee will first check to see if the table exists before playhouse.sqlite_ext import SqliteExtDatabase sqlite_db = SqliteExtDatabase('my_app.db', journal_mode='WAL') PRAGMA statements New in version 2.6.4. SQLite allows run-time configuration of a number of parameters containing the pragma name and value: db = SqliteDatabase('my_app.db', pragmas=( ('journal_mode', 'WAL'), ('cache_size', 10000), ('mmap_size', 1024 * 1024 * 32), )) SQLite and Autocommit Changed

policy for keys within the collection. This feature can be used to restrict which organizations can write data to a collection, and is what enables the new chaincode lifecycle and chaincode application patterns Hyperledger Fabric has a ledger subsystem comprising two components: the world state and the transaction log. Each participant has a copy of the ledger to every Hyperledger Fabric network they belong to. The the state of the ledger at a given point in time. It’s the database of the ledger. The transaction log component records all transactions which have resulted in the current value of the world state; it’s

0.0 ，出于安全考 虑，请根据实际业务网络情况，修改为安全的监听地址，如：内网IP或 特定的外网IP 命令执行成功会输出All completed。如果执行出错，请检查nodes/build.log 文件中的错误信息。 bash build_chain.sh -l "127.0.0.1:4" -p 30300,20200,8545 Checking fisco-bcos binary... /home/ubuntu/fisco/nodes/127.0.0.1/node3/../fisco-bcos -c config.ini tail -f nodes/127.0.0.1/node0/log/log* | grep connected 正常情况会不停地输出链接信息，从输出可以看出node0与另外3个节点有链 接。 执行下面指令，检查是否在共识 正常情况会不停输出++++Generating 17:31:18.317105| [P2P][Service] heartBeat connected count,size=3 tail -f nodes/127.0.0.1/node0/log/log* | grep +++ info|2019-01-21 17:23:32.576197| [g:1][p:264][CONSENSUS] [SEALER]++++++++++++++++Generating

jsonrpc_port， 出于安全考虑jsonrpc/channel默认监听127.0.0.1，需要外网访问请添加-i 参数。 命令执行成功会输出All completed。如果执行出错，请检查nodes/build.log 文件中的错误信息。 启动FISCO BCOS链 启动所有节点 启动成功会输出类似下面内容的响应。否则请使用netstat -an | grep tcp 检查机器的30300~30303，20 /home/fisco/fisco/nodes/127.0.0.1/node3/../fisco-bcos -c config.ini tail -f nodes/127.0.0.1/node0/log/log* | grep connected info|2019-01-21 17:30:58.316769| [P2P][Service] heartBeat connected count,size=3 17:31:18.317105| [P2P][Service] heartBeat connected count,size=3 tail -f nodes/127.0.0.1/node0/log/log* | grep +++ 配置及使用控制台 在控制台通过Web3SDK链接FISCO BCOS节点，实现查询区块链状态、部署 调用合约等功能，能够快速获取到所需要的信息。控制台指令详细介绍参考

0.0 ，出于安全考 虑，请根据实际业务网络情况，修改为安全的监听地址，如：内网IP或 特定的外网IP 命令执行成功会输出All completed。如果执行出错，请检查nodes/build.log 文件中的错误信息。 bash build_chain.sh -l "127.0.0.1:4" -p 30300,20200,8545 Checking fisco-bcos binary... /home/ubuntu/fisco/nodes/127.0.0.1/node3/../fisco-bcos -c config.ini tail -f nodes/127.0.0.1/node0/log/log* | grep connected 正常情况会不停地输出链接信息，从输出可以看出node0与另外3个节点有链 接。 执行下面指令，检查是否在共识 正常情况会不停输出++++Generating info|2019-01-21 17:31:18.317105| [P2P][Service] heartBeat,connected count=3 tail -f nodes/127.0.0.1/node0/log/log* | grep +++ info|2019-01-21 17:23:32.576197| [g:1][p:264][CONSENSUS] [SEALER]++++++++++++++++Generating