How to specify field name - symfony

I had next entity with yaml format:
BW\UserBundle\Entity\User:
type: entity
table: users
repositoryClass: BW\UserBundle\Entity\UserRepository
id:
id:
type: integer
id: true
generator:
strategy: AUTO
fields:
username:
type: string
length: 25
unique: true
password:
type: string
length: 64
email:
type: string
length: 60
unique: true
isActive:
type: boolean
lifecycleCallbacks: { }
Now, when I update scheme, I get isActive field name in DB, same as property name.
How can I specify property name isActive like is_active field name in DB?


You need to specify a column name like this:
BW\UserBundle\Entity\User:
type: entity
table: users
repositoryClass: BW\UserBundle\Entity\UserRepository
id:
id:
type: integer
id: true
generator:
strategy: AUTO
fields:
username:
type: string
length: 25
unique: true
password:
type: string
length: 64
email:
type: string
length: 60
unique: true
isActive:
type: boolean
column: is_active
lifecycleCallbacks: { }
More on that - http://docs.doctrine-project.org/en/2.0.x/reference/basic-mapping.html#property-mapping


You can specify the column name for the database
fields:
username:
type: string
length: 25
unique: true
password:
type: string
length: 64
email:
type: string
length: 60
unique: true
isActive:
type: boolean
column: is_active


You dealing with two different kind of conventions here. It is common in Symfony to use camel case for naming variables. Within databases you often find this underscore written names. If you access your isActive property your entity model will map it to the is_active column in the database.

Related

Symfony doctrine empty relation in behat tests

I have a problem with behat in symfony 2. I have two entities:
//Transaction
DM\MultiStepFormBundle\Entity\Transaction:
type: entity
repositoryClass: DM\MultiStepFormBundle\Repository\Transaction\TransactionRepository
table: rb_multistepform_transaction
indexes:
transaction_id_index:
columns: [ transaction_id ]
id:
id:
type: integer
generator: { strategy: AUTO }
fields:
created_at:
type: datetime
nullable: false
transaction_id:
type: string
length: 128
nullable: false
is_client_new:
type: boolean
options:
default: false
utm_source:
type: string
length: 255
nullable: true
utm_medium:
type: string
length: 255
nullable: true
utm_campaign:
type: string
length: 255
nullable: true
user_agent:
type: text
nullable: true
http_referer:
type: string
length: 255
nullable: true
ip:
type: string
length: 32
nullable: true
status:
type: smallint
nullable: false
options:
default: 0
continue_service_run:
type: boolean
nullable: false
options:
default: false
continue_serivce_run_datetime:
type: datetime
nullable: true
oneToMany:
items:
targetEntity: DM\MultiStepFormBundle\Entity\TransactionItem
mappedBy: transaction
cascade: [persist, merge, remove]
manyToOne:
client:
targetEntity: DM\KlienciBundle\Entity\Client
inversedBy: multistepform_transactions
joinColumn:
name: client_id
referencedColumnName: id
//TransactionItem
DM\MultiStepFormBundle\Entity\TransactionItem:
type: entity
repositoryClass: DM\MultiStepFormBundle\Repository\Transaction\TransactionRepository
table: rb_multistepform_transaction_item
id:
id:
type: integer
generator: { strategy: AUTO }
indexes:
partner_status_index:
columns: [ partner_name, status ]
fields:
type:
type: smallint
nullable: false
partner_name:
type: string
length: 128
nullable: true
status:
type: smallint
nullable: false
options:
default: 0
link_id:
type: integer
nullable: true
product_id:
type: integer
nullable: true
pixelconversion_hash:
type: string
length: 128
nullable: true
partner_api_response:
type: json_array
nullable: true
clicked:
type: boolean
nullable: false
options:
default: 0
clicked_datetime:
type: datetime
nullable: true
order_nr:
type: integer
nullable: true
highlighted:
type: boolean
nullable: false
options:
default: false
manyToOne:
transaction:
targetEntity: DM\MultiStepFormBundle\Entity\Transaction
inversedBy: items
cascade: [persist, merge, remove]
joinColumn:
name: transaction_id
referencedColumnName: id
When i testing a service where I have such loops:
$transactions = $this->transactionRepository->getTransactionsByContinueServiceRunInDateRange(0, $minDateTime, $maxDateTime);
foreach ($transactions as $transactionKey => $singleTransaction) {
//in this place, relationships are not taken
$transactionItems = $singleTransaction->getItems();
//when it performs a test query items are downloaded correctly
$transactionItemsQuery = $this->transactionRepository->getItems($singleTransaction->getId());
}
In which i needs to get items from the reverse relation. With a normal call to the site in symfony, the relationships are correct and everything is ok.
In the case of activating test in behat, relations in the variable $transactionItems are an empty collection. The data surely exists in the database because in the variable $transactionItemsQuery as I get data from query I have correct data.
Has anyone ever encountered something like that in behat?

Running function on Sonata Admin List field

In my application, backend users can segment frontend members through criteria like age, gender etc. These criteria are saved in a class called Segment.
AppBundle\Entity\Segment:
type: entity
table: segments
fields:
id:
id: true
type: integer
generator:
strategy: IDENTITY
name:
type: string
length: 300
created_at:
type: datetime
updated_at:
type: datetime
nullable: true
oneToMany:
parameters:
targetEntity: SegmentFilter
mappedBy: segment
cascade: [persist]
manyToOne:
owner:
targetEntity: Application\Sonata\UserBundle\Entity\User
inversedBy: null
joinColumn:
created_by:
referencedColumnName: id
The SegmentFilter class holds the parameters for filtering the members eg. criteria can be 'age', 'description' can be null but its for clarity purposes for whoever is reading the criteria and finally value can be '>= 30'
AppBundle\Entity\SegmentFilter:
type: entity
table: segment_filters
fields:
id:
id: true
type: integer
generator:
strategy: IDENTITY
criteria:
type: string
length: 50
description:
type: string
length: 300
value:
type: string
length: 300
manyToOne:
segment:
targetEntity: Segment
inversedBy: paramemters
joinColumn:
segmentation_id:
referencedColumnName: id
Here's the member's class to be segmented based on the parameters defined for each segment:
AppBundle\Entity\Member:
type: entity
table: members
fields:
id:
id: true
type: integer
generator:
strategy: IDENTITY
first_name:
type: string
length: 20
last_name:
type: string
length: 20
mobile:
type: string
length: 11
address:
type: string
length: 255
zip:
type: string
length: 6
town:
type: string
length: 25
email:
type: string
length: 50
dob:
type: date
In the list of segments, I would like to add an extra field that shows how many members currently fall in each segment created. How would I go about this?

Extending models with additional fields in Doctrine

I'm trying to figure out a way to extend a model in Doctrine. I have the following situation
Card Model (The base model):
Nos\CardBundle\Entity\Card:
type: entity
table: cards
inheritanceType: SINGLE_TABLE
discriminatorColumn:
name: card_type
type: string
discriminatorMap:
staff: Nos\StaffBundle\Entity\Staff
supplier: Nos\SupplierBundle\Entity\Supplier
id:
id:
id: true
type: integer
length: 11
generator:
strategy: AUTO
options:
unsigned: true
fields:
user_id:
type: integer
length: 11
nullable: true
options:
unsigned: true
card_display_name:
type: string
length: 255
nullable: false
I discriminate the model using the card_type property. When it's 'staff', it should return a Staff model, when it's 'supplier' it should return a Supplier Model
Staff Model (Extends Card model)
Nos\StaffBundle\Entity\Staff:
type: entity
inheritance:
extends: Nos\CardBundle\Entity\Card
type: simple
staff_initials:
type: string
length: 15
staff_baptismal_names:
type: string
length: 255
and the Supplier model
Nos\StaffBundle\Entity\Supplier:
type: entity
inheritance:
extends: Nos\CardBundle\Entity\Card
type: simple
supplier_name:
type: string
length: 255
When I generate the tables, the additional fields in Supplier and Staff models are not being created. Do I have to define those additional fields in the Card model? And if so, how can I exclude them from the models that they don't belong to?

symfony2: trying to update the entities using "doctrine:generate:entities"

I have this file:
#src/Jander/JanderBundle/resources/config/doctrine/metadata/orm/
Propuestas.orm.yml
Propuestas:
type: entity
table: propuestas
fields:
id:
id: true
type: integer
unsigned: false
nullable: false
generator:
strategy: IDENTITY
contenido:
type: string
length: 230
fixed: false
nullable: false
lifecycleCallbacks: { }
I have just added a new field like this:
Propuestas:
type: entity
table: propuestas
fields:
id:
id: true
type: integer
unsigned: false
nullable: false
generator:
strategy: IDENTITY
contenido:
type: string
length: 230
fixed: false
nullable: false
contenido2:
type: string
length: 230
fixed: false
nullable: false
lifecycleCallbacks: { }
and then I'm trying to generate the entity with the new field and I
get this:
$ php app/console doctrine:generate:entities "JanderJanderBundle"
backing up Propuestas.php to Propuestas.php~
generating Volumus\VolumusBundle\Entity\Propuestas
but when I open Propuestas.php there isn't any reference about
"contenido2".
Any idea?

Clearing the cache solves the problem. This is strange, make sure your cache permissions are fine.

Entity class not found when trying to create entities from yml config files

I'm trying to create entity classes. I am using yml files from Resources/config/doctrine folder.
Category.orm.yml
Marek\JobeetBundle\Entity\Category:
type: entity
table: null
fields:
id:
type: integer
id: true
generator:
strategy: IDENTITY
name:
type: string
length: '255'
unique: true
manyToMany:
affiliates:
targetEntity: Marek\JobeetBundle\Entity\Affiliate
joinTable:
name: CategoryAffiliate
joinColumns:
category_id:
referencedColumnName: id
inverseJoinColumns:
affiliate_id:
referencedColumnName: id
lifecycleCallbacks: { }
Affilate.orm.yml
Marek\JobeetBundle\Entity\Affiliate:
type: entity
table: null
fields:
id:
type: integer
id: true
generator:
strategy: IDENTITY
url:
type: string
length: '255'
nullable: true
email:
type: string
length: '255'
nullable: true
unique: true
token:
type: string
length: '255'
isActive:
type: boolean
nullable: false
column: is_active
default: 0
createdAt:
type: datetime
column: created_at
gedmo:
timestampable:
on: create
manyToMany:
categories:
targetEntity: Marek\JobeetBundle\Entity\Category
mappedBy: affiliates
lifecycleCallbacks: { }
Job:
Marek\JobeetBundle\Entity\Job:
type: entity
table: null
fields:
id:
type: integer
id: true
generator:
strategy: IDENTITY
type:
type: string
length: '255'
company:
type: string
length: '255'
nullable: true
logo:
type: string
length: '255'
url:
type: string
length: '255'
nullable: true
position:
type: string
length: '255'
nullable: true
location:
type: string
length: '255'
description:
type: string
length: '4000'
howToApply:
type: string
length: '4000'
column: how_to_apply
token:
type: string
length: '255'
unique: true
isPublic:
type: boolean
length: null
column: is_public
isActivated:
type: boolean
length: null
column: is_activated
email:
type: string
length: '255'
createdAt:
type: datetime
column: created_at
gedmo:
timestampable:
on: create
updatedAt:
type: datetime
column: updated_at
gedmo:
timestampable:
on: update
expiresAt:
type: datetime
column: expires_at
oneToOne:
category:
targetEntity: Marek\JobeetBundle\Entity\Category
cascade: { }
mappedBy: null
inversedBy: null
joinColumns:
category_id:
referencedColumnName: id
orphanRemoval: false
lifecycleCallbacks: { }
After executing:
php app/console doctrine:generate:entities JobeetBundle --path="src"
I am getting:
Warning: class_parent(): Class Marek\JobeetBundle\Entity\Affiliate
does not exists and could not be loaded in
vendor/gedmo-doctrine-extension\lib\Gedmo\Mapping\ExtensionMetadataFactory.php
on line 80.
I know that I have not any entities I want to create them.
Could somebody help?

This may be caused by an invalid assumption in Gedmo. Try commenting out the entire stof_doctrine_extensions block in your config.yml and then running the generate command. If it works, you should be able to uncomment the config and get back to work.

Resources