[FLOW3-general] DateTime limited to Unix timestamp?

Martin Kutschker masi-no at spam-typo3.org
Mon Oct 11 09:26:28 CEST 2010


Am 10.10.2010 23:43, schrieb Jigal van Hemert:
> On 10-10-2010 20:04, Martin Kutschker wrote:
>> Am 09.10.2010 15:16, schrieb Jigal van Hemert:
>>> If FLOW3 will support raw queries there will be less need to make a feature rich API, because
>>> problems can easily be solved with raw queries.
> 
> Maybe I have to explain to some that I meant this not as an opinion for support of raw queries, but
> as a warning that support of raw queries will have consequences for an entire product later on: as
> soon as there are a few major "extensions" available which use raw queries it is less likely that
> they will ever be removed and thus the product is kind of locked to a limited number of supported
> DBMSs.

Good.

>> IMHO FLOW3 should allow raw SQL only for one reason: performance. At a certain point in the
>> development/deployment you may find yourself in the need of streamlining the disc/DB access.
> 
> The most performance gain can be found in optimizing algorithms.

That really depends on the nature of the bottle neck. But I think we agree that you shall only tune
after deployment and with proper profiling. If something can be done by changing the algorithms
fine, if it's the DB you have to bite the bullet.

>> An interesting question is if FLOW3 should provide a DBAL like API for that. If you really want to
>> tune the system you probably want to get the most of the features of your RDBMS. So you don't want
>> an extra layer between your SQL and the DB.
> 
> If you mean a DBAL like v.4 has, then please no. With all due respect to the creators and
> maintainers of this system extension, but the way it is built (a rewrite engine for queries) was
> necessary because the system allowed raw queries.

Actually I was more thinking in terms of ADOdb.

> For an enterprise level system it's actually more important that it runs on a wide range of systems
> than that it has a bit extra performance.

I wasn't thinking about a bit of extra performance but real problems. Even Evans didn't shy away
from DB access if really necessary. At least that's the way I understood it.

Masi


More information about the FLOW3-general mailing list