thebuggenie/b2db

b2db

b2db's Issues

Bug in vendor/thebuggenie/b2db/src.core.php

Hi,
I made a mistake in my DSN during an upgrade.

This causes a 500 error.

It was caused by line 382:

//throw new B2DBException('This does not look like a valid DSN - cannot read the connection details');

I replaced this replaced this with:

throw new Exception('This does not look like a valid DSN - cannot read the connection details');

And all is good now.

Valid SQL Query is rejected

Hi,
I've just tried to update The Buggenie from 3.2.7 to 4.0 on the way to 4.1 (the straight through upgrade failed).

I am currently getting an error on navigating to the page as follows

An error occurred in The Bug Genie
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'listtypes listtypes0 LEFT JOIN scopes scopes1 ON (scopes1.id=lis' at line 1
An exception was thrown in the B2DB framework
"
SQL:

SELECT listtypes0.name AS listtypes0_name, listtypes0.itemtype AS listtypes0_itemtype, listtypes0.itemdata AS listtypes0_itemdata, listtypes0.sort_order AS listtypes0_sort_order, listtypes0.key AS listtypes0_key, listtypes0.scope AS listtypes0_scope, listtypes0.id AS listtypes0_id, scopes1.name AS scopes1_name, scopes1.description AS scopes1_description, scopes1.enabled AS scopes1_enabled, scopes1.uploads_enabled AS scopes1_uploads_enabled, scopes1.max_upload_limit AS scopes1_max_upload_limit, scopes1.custom_workflows_enabled AS scopes1_custom_workflows_enabled, scopes1.max_workflows AS scopes1_max_workflows, scopes1.max_users AS scopes1_max_users, scopes1.max_projects AS scopes1_max_projects, scopes1.max_teams AS scopes1_max_teams, scopes1.id AS scopes1_id, scopes2.name AS scopes2_name, scopes2.description AS scopes2_description, scopes2.enabled AS scopes2_enabled, scopes2.uploads_enabled AS scopes2_uploads_enabled, scopes2.max_upload_limit AS scopes2_max_upload_limit, scopes2.custom_workflows_enabled AS scopes2_custom_workflows_enabled, scopes2.max_workflows AS scopes2_max_workflows, scopes2.max_users AS scopes2_max_users, scopes2.max_projects AS scopes2_max_projects, scopes2.max_teams AS scopes2_max_teams, scopes2.id AS scopes2_id FROM listtypes listtypes0 LEFT JOIN scopes scopes1 ON (scopes1.id=listtypes0.scope) LEFT JOIN scopes scopes2 ON (scopes2.id=listtypes0.scope) WHERE (listtypes0.itemtype = 'status') "

But this query is valid and works when I copy it to say phpmyadmin. I get results as expected.

This error seems to be in B2DB.

Thanks for help.
Barry

Don't use sql cache for Query when generating SQL

There is at least one bug in The Bug Genie bugtracker cause by Query checking already generated sql string.

Here you can see working not as expected code because Query already compiled as SELECT statement here and actually not deleting anything.

Of course you can try to make some kind of complex cache validating but I don't think it's worth it.

How to reproduce(pseudo code):

$query = Query();
$query->where(<add some conditions>);

$result = $table->select($query);

// instead of deleting actually will be executed last Select query
$table->delete($query);

or few same action with a little bit changed Query:

$query = Query();
$query->where(<add some conditions>);

$result1 = $table->select($query);

$query->where(<add some another conditions>);

// actually will be executed previous Select query
$result2 = $table->select($query);