querybuilder

There are few things which you need to change in your code.

1. when using Formik there is no need to maintain state explicitly to hold the form values . Formik will take care of it .

2. You are just changing the values but not notifying the formik to change its state.

3. Since you are rendering the array of Fields , you can make use of the Formik FieldArray component which comes with the bunch of helpers like pushing a new row, removing the row and updating the value of a field within each row.

4. Your submit was not working because you have the submit button outside the component . So clicking on submit button will not call the onSubmit of Formik .

Have refactored your code to make use of the FieldArray .

Working codesandbox

The warning message is not related to the DB switch mechanism.

Try to change your select statement to something like:

Overriding the Grammer class directly may be possible but it internally delegates its work to Database Specific grammer classes

For example if you have configured Mysql in config/database.php then the Grammer class delegates the work on to Illuminate\Database\Query\Grammars\MySqlGrammar

Similarly for Postgres it will be Illuminate\Database\Query\Grammars\PostgresGrammar

Based on the database config the ConnectionFactory[src/Illuminate/Database/Connectors/ConnectionFactory.php->createConnection()]

loads the proper connection manager for a given database

I am not sure if overriding of this classes is even possible or not because of the PSR-4 loading as the namespace is tightly linked with the physical location of the file in the directory tree

So instead of that I would suggest to go for laravel macros by which you may add new functions to existing classes that use Macroable trait

A POC example can be found below, for further advancement you are encouraged to dig the code for update, insert, delete etc in Grammer.php and Builder.php

Above code is indeed working, confirmed using TypeORM's logging, it shows the transaction starting and all the following queries before committing.

More info on how to enable Logging and to verify if your queries are under the same transaction: https://github.com/typeorm/typeorm/blob/master/docs/logging.md

To check if all options should exist for the ad you will need to use aggregation and filter on aggregated result

Yes you are right, this is for the filtering by types. These types are e.g. the template-keys for pages and the title is for the translation in the admin ui.

The selected types can be used in your CustomDataProvider with the Sulu/Component/Content/SmartContent/QueryBuilder to filter the items by a specific type.

The DataProviderRepositoryTrait uses the type-filtering on the these lines. You can also overwrite the appendTypeRelation method, if the alias is not correct for your custom entity.

But if you don't need filtering by types, you can just ignore it.

As answered in #3542

DQL is about querying objects. Supporting subselects in the FROM clause means that the DQL parser is not able to build the result set mapping anymore (as the fields returned by the subquery may not match the object anymore).

Your best bet would be to use sql instead

If a user wants to search across multiple dimensions/indexes then MultiSearch will be very useful.

Example Usage: User can search for 'java' in person, article & job indices (in a LinkedIn type application) and would be able to configure pagination per request.

You can use like this