Niels Braczek

See https://github.com/jmorganca/ollama/issues/618#issuecomment-1737547046 The `num_gpu` parameter solved the problem for me. On my machine (only 12G), ollama loaded 43 layers and failed with the same error as above, but runs smooth...

This would be possible only, if either PostgreSQL supports that, too, or we can (want to) mimic that for PostgreSQL. I'm not very much into that subject, so I leave...

We need to define when to use the UPDATE fallback. I'd suggest to use REPLACE (which MySQL supports since ages), See https://dev.mysql.com/doc/refman/8.0/en/replace.html The behaviour would be different, though, as the...

> I'd maybe use something like insertOrUpdateObject and query->onDuplicateKeyUpdate regarding the naming. I like the names as they are self-explanatory. The problem I see is that we cannot safely provide...

Yes, MS SQL Server. To drop it, we need an official decision by the Production Department.

> You are basically saying that because of the lack of scalar typehints, the API contract is now `stringToObject(mixed $data, array $options): mixed` (contradictory to the documented API) The API...

Got your point. I tend to agree with your view. But then we have to make that clearer in the documentation. I will bring this up for discussion at the...

That is expected behaviour. After ```php $app->setHeader('Some-Header', 'This should be used', true); $app->setHeader('Some-Header', 'This should not be used', false); ``` the value of the header is ``` Array ( 'Some-Header'...

> @nibra Why are all values not output then? That depends on the actual header definition. Some accept multiple values, some don't.

See joomla/joomla-cms#16528 for related discussion