Download the PHP package eloquent/fixie without Composer
On this page you can find all versions of the php package eloquent/fixie. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package fixie
No longer maintained
This package is no longer maintained. See this statement for more info.
Fixie
YAML-based data fixtures.
Installation and documentation
- Available as Composer package eloquent/dumpling.
- API documentation available.
What is Fixie?
Fixie is a format for storing tabular data. It blends the strengths of YAML and CSV to produce a syntax that is well suited for both human and machine readers.
The Fixie syntax is actually a subset of YAML 1.2, meaning that any given example of Fixie syntax is also perfectly valid YAML. Unlike free-form YAML however, all Fixie variants can be read row-by-row, which allows for minimal memory usage when reading large amounts of data.
Output styles
Compact style
The default style, recommended for data sets of any size.
Expanded style
This style is useful for small data sets where a more vertical layout improves human readability.
Output style variants
Fixie implements multiple output styles. In addition to the 'aligned' output styles above, there are non-aligned variants of both compact and expanded styles that reduce file size at the cost of reduced human readability.
The FixtureWriter class takes, as its first constructor parameter, a class
name to use when opening a file or stream for writing. The options available
are (in the Eloquent\Fixie\Writer namespace):
SwitchingCompactFixtureWriteHandle
This variant will buffer up to an approximate given data size (defaults to 10MiB). If the data written is within the size limit, the output will be that produced by the AlignedCompactFixtureWriteHandle. If the size limit is exceeded, this variant will switch to unbuffered output using the CompactFixtureWriteHandle.
This is the default variant used by Fixie, as it offers the best compromise between memory usage and human readability.
AlignedCompactFixtureWriteHandle
Writes rows in the 'compact' style, and keeps column headers and row values aligned with each other. This style is excellent for human readability but poor for large data sets as the data must be buffered in memory. Unless the maximum data size is known in advance, it is recommended to use the SwitchingCompactFixtureWriteHandle instead.
CompactFixtureWriteHandle
Writes rows in the 'compact' style, using the minimal amount of whitespace. This variant is excellent for any data size, but is not as good for human readability as other options. If human readability is not an issue, use this variant.
AlignedExpandedFixtureWriteHandle
Writes rows in the 'expanded' style, and aligns row values. A versatile variant that produces a much more vertically elongated output. Good for both human readability and memory usage.
ExpandedFixtureWriteHandle
Writes rows in the 'expanded' style, but does not align row values. Only useful if the data should be output in a similar way to typical YAML renderers.
Usage
A little setup
Writing row-by-row
Writing an entire set of data
Reading row-by-row
Reading an entire set of data
Reading rows manually
Opening streams
Comparison to CSV and YAML
CSV
- Excellent for machine reading. Row-by-row reading means low memory use.
- No support for types. Every value is a string.
- Human readability is poor, especially with row values of differing lengths.
- String encoding support is unpredictable across implementations. This makes it a poor choice for multilingual data.
YAML
- Type support. Strings, integers, floating-point values, booleans and nulls are all supported.
- Very human-readable when formatted correctly.
- Good string encoding support.
- Entire file must be read and parsed in one go. Memory usage scales with data size.
Fixie
- Excellent for machine reading. Row-by-row reading means low memory use.
- Type support. Strings, integers, floating-point values, booleans and nulls are all supported.
- Very human-readable when formatted correctly.
- Good string encoding support.
