Can anyone help me to understand second step

U03DQ4D8L65

Can anyone help me to understand second step https://github.com/spryker/spryker-docs/blob/master/docs/scos/dev/back-end-develop[…]estion/structural-preparations/extending-the-database-schema.md ?

Oleksandr Peresypkin

In the second step here, you can add columns to extend the table. Perhaps this documentation https://propelorm.org/Propel/reference/schema.html would help you get familiar with Propel schema definition.

U03DQ4D8L65

@U02NPALT127 - Can we change spy_product_table to some custom name like ab_product_table for custom table?

Oleksandr Peresypkin

well, I’m not sure if it’s possible without rewriting core modules

U03DQ4D8L65

Ok

U03DQ4D8L65

@U02NPALT127 we cannot modify the OOTB table only the custom tabels need to be named as awn_?

Oleksandr Peresypkin

you can use a custom namespace as it’s stated in https://docs.spryker.com/docs/scos/dev/guidelines/project-development-guidelines.html#use-custom-namespaces and use Awn instead of Pyz.
Rename it in:

$config[KernelConstants::PROJECT_NAMESPACE] = 'Pyz';
$config[KernelConstants::PROJECT_NAMESPACES] = [
    'Pyz',
];

But if you already have the codebase in the Pyz namespace, it should be replaced with Awn everywhere as well

U03DQ4D8L65

Is it reflect for all place correct?

Oleksandr Peresypkin

yes, on the project level

U03DQ4D8L65

Ok Thanks