forcément vers un nouveau blog. Mais pas que puisque le but de coolkeums est de pouvoir créer un moteur de gestion de contenu orienté recherche afin de garder la main sur mes sacro saintes informations personnelles sur internet.
Rendez vous la bas pour de nouvelles aventures geek.
#!/bin/bash args=$*; if [ -z "${args[*]}" ]; then echo "no URL given" exit 1 fi # strip the vim:// url=${args[*]:6}; # grab the left part of the : file=$(echo $url | awk -F':' '{print $1}') # there might be a servername separated with @ servername=$(echo $file | awk -F'@' '{print $2}') # if not, the session name is VIM servername=${servername:="VIM"} servername="--servername $servername" # grab the file file=$(echo $file | awk -F'@' '{print $1}') # grab the line number and set the option if any line=$(echo $url | awk -F':' '{print $2}') line=${line:+"+${line}"} gvim $servername --remote-tab-silent $line $file
What happens here ? We do grab the file and the optional line number and session name from the URL and launch gvim with the «remote» option. This means if you have a Vim session running in a terminal it will open a new tab with the file at the given location, otherwise this will pop up a gvim window with the file at the right place.
Note that you can do the same thing for x-debug error messages ! This awsome trick is well explained here.
shell$ mv frontend.php frontend_prod.php
shell$ ln -s frontend_dev.php !:1
ln -s frontend_dev.php frontend.php
| marqueur | pseudo | fichier |
| S | Schéma | /config/schema.yml |
| F | Fixtures | /data/fixtures/fixtures.yml |
| A | Action | /apps/appli_courante/modules/module_courant/actions/actions.class.php |
| R | Routing | /apps/appli_courante/config/routing.yml |
Vehicle:
tableName: vehicle
actAs: [Timestampable]
columns:
ref: { type: char(6), primary: true }
brand: { type: varchar(255), notnull: true }
Bicycle:
inheritance: { type: simple, extends: Vehicle }
columns:
bike_type: { type: enum, values: [city, mountain, race], default: city, notnull: true }
gears: { type: integer(32), default: 1, notnull: true }
seats: { type: integer(4), default: 1, notnull: true }
checks:
gears_min: gears > 0
seats_min: seats >
CREATE TABLE vehicle ((Our check statements do no appear) It sounds rather limited but let's see what we can do with that, assuming we add 2 bikes in the database using fixtures:
ref CHAR(6),
brand VARCHAR(255) NOT NULL,
bike_type VARCHAR(255) DEFAULT 'city' NOT NULL,
gears BIGINT DEFAULT 1 NOT NULL,
seats INT DEFAULT 1 NOT NULL,
created_at TIMESTAMP without time zone,
updated_at TIMESTAMP without time zone,
PRIMARY KEY(ref)
);
./symfony doctrine:dql "SELECT * FROM Bicycle"
>> doctrine executing dql query
DQL: SELECT * FROM Bicycle
found 2 results
-
ref: BK0478
brand: peugeot
bike_type: city
gears: '4'
seats: 1
created_at: '2009-01-04 17:18:25'
updated_at: '2009-01-04 17:18:25'
-
ref: BK0734
brand: raleigh
bike_type: mountain
gears: '21'
seats: 1
created_at: '2009-01-04 17:18:25'
updated_at: '2009-01-04 17:18:25
Bicycle:Launche the build-all-reload and see what we have:
inheritance: { type: concrete, extends: Vehicle }
CREATE TABLE vehicle (It sounds like Doctrine has created two tables and wants to handle the inheritance by itself. Let's see what we have once the fixtures are loaded:
ref CHAR(6),
brand VARCHAR(255) NOT NULL,
created_at TIMESTAMP without time zone,
updated_at TIMESTAMP without time zone,
PRIMARY KEY(ref)
);
CREATE TABLE bicycle (
ref CHAR(6),
brand VARCHAR(255) NOT NULL,
bike_type VARCHAR(255) DEFAULT 'city' NOT NULL,
gears BIGINT DEFAULT 1 NOT NULL,
seats INT DEFAULT 1 NOT NULL,
created_at TIMESTAMP without time zone,
updated_at TIMESTAMP without time zone,
PRIMARY KEY(ref),
CHECK (gears > 0),
CHECK (seats > 0)
);
dbtest=> \dWe can see we have 2 bikes but it also appears we have no vehicules ! So Doctrine does not handle the inheritance by itself, if we want to have 2 bikes and also say we have 2 vehicles we have to overload the Bicycle definition. The other solution is to declare the Vehicle as an abstract class:
List of relations
Schema | Name | Type | Owner
--------+---------+-------+-------
public | bicycle | table | toto
public | vehicle | table | toto
(2 rows)
dbtest=> SELECT * FROM vehicle ;
ref | brand | created_at | updated_at
-----+-------+------------+------------
(0 rows)
dbtest=> SELECT * FROM bicycle ;
ref | brand | bike_type | gears | seats | created_at | updated_at
--------+---------+-----------+-------+-------+---------------------+---------------------
BK0478 | peugeot | city | 4 | 1 | 2009-01-04 17:25:26 | 2009-01-04 17:25:26
BK0734 | raleigh | mountain | 21 | 1 | 2009-01-04 17:25:26 | 2009-01-04 17:25:26
(2 rows)
Vehicle:But this seems not to work (or I missunderstood the doc) because the table definition is still present in the SQL...
tableName: vehicle
abstract: true
Motorcycle:So after adding some fixtures I have 2 tables with independant data:
inheritance: { type: concrete, extends: Vehicle }
columns:
type: { type: enum, values: [scooter, roadster, city], notnull: true, default: scooter }
cylinder: { type: integer, notnull: true }
plate: { type: string(11), notnull: true, unique: true }
checks:
cylinder_min: cylinder > 0
plate_format: plate ~ \'[0-9]{1,4}\\-[A-Z]{2,3}\\-[0-9]{1,2}\
dbtest=> SELECT * FROM motorcycle ;If I try to count the vehicles I have with a DQL query it would not be as simple as:
ref | brand | type | cylinder | plate | created_at | updated_at
--------+--------+---------+----------+------------+---------------------+---------------------
MB1837 | vespa | scooter | 125 | 324-MA-92 | 2009-01-08 19:37:10 | 2009-01-08 19:37:10
MB6430 | yamaha | city | 750 | 2301-ZC-60 | 2009-01-08 19:37:10 | 2009-01-08 19:37:10
(2 rows)
dbtest=> SELECT * FROM bicycle ;
ref | brand | bike_type | gears | seats | created_at | updated_at
--------+---------+-----------+-------+-------+---------------------+---------------------
BK0478 | peugeot | city | 4 | 1 | 2009-01-08 19:37:10 | 2009-01-08 19:37:10
BK0734 | raleigh | mountain | 21 | 1 | 2009-01-08 19:37:10 | 2009-01-08 19:37:10
(2 rows)
dbtest=> SELECT * FROM vehicle ;
ref | brand | created_at | updated_at
-----+-------+------------+------------
(0 rows)
test$ ./symfony doctrine:dql "SELECT * FROM Vehicle"
>> doctrine executing dql query
DQL: SELECT * FROM Vehicle
>> doctrine no results found
Bicycle:For the bicycles and
inheritance: { type: column_aggregation, extends: Vehicle, keyField: type, keyValue: bicycle }
Motorcycle:for the motorbikes.
inheritance: { type: column_aggregation, extends: Vehicle, keyField: type, keyValue: motorbike }
dbtest=> SELECT * FROM vehicle ;At the end of this testing phase I am a bit confused about what these types of inheritance stand for. I am not sure I will ever use one of those. I was expecting Doctrine to have like a PHP implementation of what Postgresql's inheritance system is without the problems it has ... or maybe I am missing something :o)
ref | brand | type | bike_type | gears | seats | cylinder | plate | created_at | updated_at
-----+-------+------+-----------+-------+-------+----------+-------+------------+------------
(0 rows)
| Mars 2014 | ||||||||||
| L | M | M | J | V | S | D | ||||
| 1 | 2 | |||||||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 | ||||
| 10 | 11 | 12 | 13 | 14 | 15 | 16 | ||||
| 17 | 18 | 19 | 20 | 21 | 22 | 23 | ||||
| 24 | 25 | 26 | 27 | 28 | 29 | 30 | ||||
| 31 | ||||||||||
|
||||||||||
