You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a matter of fact, it's doing a prepare + execute.
If it does not, couldn't a multi or another method do that, instead of just returning an error? It does not seem fair to force the user to do a prepare + execute.
The text was updated successfully, but these errors were encountered:
In Perl the DBI module avoids prepare/execute for do() statements. They are generally executed directly. It appears to be largely a work-around for drivers which cannot prepare DDL commands.
Raku doesn't have any of those drivers yet and the driver should probably handle it transparently by letting prepare() do different things internally.
Also, both README.pod and examples/*p6 files show my $sth = $dbh.do(...). That's actually incorrect as it returns the number of records modified (in at least some cases) and does not return a statement handle; but I think the docs have the right approach and the code should be changed.
Aparently, it's just a matter of adding a "return" in the two alternative statements.
https://github.com/raku-community-modules/DBIish/blob/master/lib/DBDish/Connection.pm6#L103-L119
As a matter of fact, it's doing a prepare + execute.
If it does not, couldn't a multi or another method do that, instead of just returning an error? It does not seem fair to force the user to do a prepare + execute.
The text was updated successfully, but these errors were encountered: