PHPinnacle Rosetta

phpinnacle/rosetta reads the internal metadata storage used by 1C:Enterprise infobases and translates its positional serialization into typed, immutable PHP objects. It has no Laravel, Filament, or other framework dependencies.

Features

• Reads and inflates Params/DBNames and Config directly from an infobase.
• Parses the positional text serialization used by 1C configuration storage.
• Maps configuration UUIDs to physical database table and column names.
• Describes catalogs, documents, tabular sections, enumerations, accumulation registers, and information registers.
• Represents system columns and custom properties with typed field objects.
• Resolves defined types and composite field definitions.
• Supports table filtering, progress callbacks, and bounded chunk reads.
• Provides a native PDO adapter and a small connection contract for other database clients.

Installation

composer require phpinnacle/rosetta

Rosetta requires PHP 8.4, PDO, and zlib. The source database must contain the standard 1C Params and Config tables.

Reading metadata with PDO

use PDO;
use PHPinnacle\Rosetta\Connections\PdoConnection;
use PHPinnacle\Rosetta\MetadataLoader;
use PHPinnacle\Rosetta\SerializedDataParser;

$pdo = new PDO(
    'pgsql:host=127.0.0.1;port=5432;dbname=infobase',
    'username',
    'password',
    [PDO::ATTR_ERRMODE => PDO::ERRMODE_EXCEPTION],
);

$connection = new PdoConnection($pdo);
$loader = new MetadataLoader(new SerializedDataParser);

foreach ($loader->load($connection) as $metadata) {
    echo json_encode(
        $metadata,
        JSON_PRETTY_PRINT | JSON_UNESCAPED_UNICODE | JSON_THROW_ON_ERROR,
    );
}

The connection is only used for read queries. Rosetta does not create tables, persist parsed metadata, or manage the PDO lifecycle.

Filtering and progress

Pass physical table names to restrict a read. Names are matched case-insensitively and may also be passed as file paths with an extension.

$metadata = $loader->load(
    $connection,
    only: ['_reference259', '_document638'],
    progress: function (int $processed, int $total) {
        printf("%d of %d\n", $processed, $total);
    },
);

The progress callback is invoked once before reading metadata and after every root object.

Chunked reads

Storage and defined-type maps can be prepared once and reused across bounded chunks. This is useful when a consumer wants to coordinate work through its own queue or batch system.

$storageMap = $loader->storageMap($connection);
$typeMap = $loader->typeMap($connection);
$total = $loader->count($storageMap);

for ($offset = 0; $offset < $total; $offset += 100) {
    $chunk = $loader->chunk(
        $connection,
        $storageMap,
        $typeMap,
        offset: $offset,
        limit: 100,
    );
}

Metadata model

Each root object is returned as PHPinnacle\Rosetta\Data\MetadataDefinition. A definition contains its 1C identifier, physical name and code, metadata kind, logical name, localized title, system fields, and custom properties. Documents may contain tabular section definitions, while enumerations may contain possible values.

Fields implement PHPinnacle\Rosetta\Contracts\Field and expose their semantic type and referenced metadata targets. Definitions, properties, values, and fields implement JsonSerializable, so they can be encoded directly.

Custom database connections

Consumers that do not use PDO can implement PHPinnacle\Rosetta\Contracts\Connection. Rosetta passes SQL and positional bindings to select() and selectOne() and expects rows as objects.

Scope

Rosetta intentionally contains no persistence, queue, console, translation, or UI integration. Consumers remain responsible for those application-level concerns.

Testing

composer install
composer test

License

See License File.