Is my application vulnerable to SQL injection if I don’t specify each type in Doctrine2?

I thought Doctrine 2 DBAL prepared statements were safe from SQLi. But I found this confusing bit in the docs:

Is my application vulnerable to SQL injection if I don’t specify each type in Doctrine2?

I thought Doctrine 2 DBAL prepared statements were safe from SQLi. But I found this confusing bit in the docs:

Is my application vulnerable to SQL injection if I don’t specify each type in Doctrine2?

I thought Doctrine 2 DBAL prepared statements were safe from SQLi. But I found this confusing bit in the docs:

Is my application vulnerable to SQL injection if I don’t specify each type in Doctrine2?

I thought Doctrine 2 DBAL prepared statements were safe from SQLi. But I found this confusing bit in the docs:

Is my application vulnerable to SQL injection if I don’t specify each type in Doctrine2?

I thought Doctrine 2 DBAL prepared statements were safe from SQLi. But I found this confusing bit in the docs:

Building a DBAL from scratch

I am considering building a DBAL from scratch with PHP to use within my projects and also to learn through the process.

Building a DBAL from scratch

I am considering building a DBAL from scratch with PHP to use within my projects and also to learn through the process.

Building a DBAL from scratch

I am considering building a DBAL from scratch with PHP to use within my projects and also to learn through the process.

Building a DBAL from scratch

I am considering building a DBAL from scratch with PHP to use within my projects and also to learn through the process.

Doctrine 2 and Concrete table inheritance

I use Doctrine 2 and I’ve read some articles on inheritance strategies’ mapping with ORM.
I’ve seen three main strategies : “Class table inheritance”, “Concrete table inheritance” and “Single table inheritance”.