Made some changes to respect the last bundle directory structure

This commit is contained in:
William DURAND 2011-04-19 14:49:02 +02:00
parent 2cd58d70e1
commit 90fd7a91c3
3 changed files with 69 additions and 2 deletions

View file

@ -12,6 +12,7 @@ Currently supports:
* Migrations [Propel 1.6](http://www.propelorm.org/wiki/Documentation/1.6/Migrations).
* Reverse engineering from [existing database](http://www.propelorm.org/wiki/Documentation/1.6/Existing-Database).
* Integration to the Symfony2 Profiler.
* Load XML fixtures.
Installation
------------
@ -68,6 +69,9 @@ Sample Configuration
phing_path: "%kernel.root_dir%/../vendor/phing"
# charset: "UTF8"
# logging: %kernel.debug%
# build_properties:
# xxxxx.xxxxx: xxxxxx
# xxxxx.xxxxx: xxxxxx
# in app/config/config*.yml
propel:
@ -207,11 +211,30 @@ You can dump data from your database in XML to `app/propel/dump/xml/`:
Once you ran `propel:data-dump` you can generate SQL statements from dumped data:
> php app/console propel:data-sql [--connection[="..."]]
> php app/console propl:data-sql
SQL will be write in `app/propel/sql/`.
### Fixtures
You can load your own fixtures by using the following command:
> php app/console propel:load-fixtures [-d|--dir="..."] [--connection[="..."]]
As usual, `--connection` allows to specify a connection.
The `--dir` option allows to specify a directory containing the fixtures (default is: `app/propel/fixtures/`).
Note that the `--dir` expects a relative path from the root dir (which is `app/`).
A valid _XML fixtures file_ is:
<?xml version="1.0" encoding="utf-8"?>
<dataset name="all">
<Object Id="..." />
</dataset>
### Graphviz
You can generate **Graphviz** file for your project by using the following command line:

View file

@ -12,6 +12,7 @@ Currently supports:
* Migrations [Propel 1.6](http://www.propelorm.org/wiki/Documentation/1.6/Migrations).
* Reverse engineering from [existing database](http://www.propelorm.org/wiki/Documentation/1.6/Existing-Database).
* Integration to the Symfony2 Profiler.
* Load XML fixtures.
Installation
------------
@ -68,6 +69,9 @@ Sample Configuration
phing_path: "%kernel.root_dir%/../vendor/phing"
# charset: "UTF8"
# logging: %kernel.debug%
# build_properties:
# xxxxx.xxxxx: xxxxxx
# xxxxx.xxxxx: xxxxxx
# in app/config/config*.yml
propel:
@ -207,11 +211,30 @@ You can dump data from your database in XML to `app/propel/dump/xml/`:
Once you ran `propel:data-dump` you can generate SQL statements from dumped data:
> php app/console propel:data-sql [--connection[="..."]]
> php app/console propl:data-sql
SQL will be write in `app/propel/sql/`.
### Fixtures
You can load your own fixtures by using the following command:
> php app/console propel:load-fixtures [-d|--dir="..."] [--connection[="..."]]
As usual, `--connection` allows to specify a connection.
The `--dir` option allows to specify a directory containing the fixtures (default is: `app/propel/fixtures/`).
Note that the `--dir` expects a relative path from the root dir (which is `app/`).
A valid _XML fixtures file_ is:
<?xml version="1.0" encoding="utf-8"?>
<dataset name="all">
<Object Id="..." />
</dataset>
### Graphviz
You can generate **Graphviz** file for your project by using the following command line:

21
Resources/meta/LICENSE Normal file
View file

@ -0,0 +1,21 @@
The MIT License
Copyright (c) 2010-2011 william.durand1@gmail.com
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.