[RFC] - mysql-native rewrite

Kagamin spam at here.lot
Mon Sep 30 03:34:24 PDT 2013


On Sunday, 29 September 2013 at 15:42:10 UTC, simendsjo wrote:
> the previous, but is this the best way? If we choose to 
> disallow new commands, that means the user have to explicitly 
> close a lazy command.

If a command isn't closed as soon as possible, it sounds like a 
resource leak. If you silently cancel previous query, it can hide 
logical bug.

> If using classes, we can safely have several instances for a 
> command (is this neccessary?)

If you execute the same query repeatedly, there's no need to 
build the same command every time.

> The problem is that MySQL is inconsistent here, and it depends 
> on if it's a field or a constant. SELECT TRUE is not the same 
> as SELECT boolean_field.
> Also, it seems every constant integer is returned as LONGLONG. 
> But.. The fields include a length property..

Is there some hint it's true and not something else?


More information about the Digitalmars-d mailing list