← Back to team overview

drizzle-discuss team mailing list archive

Re: GSoC 2012 Client side query parsing with handlersocket/memcache API

 

Marcus: Perhaps drizzle-jdbc is also susceptible to this bug?
https://bugs.launchpad.net/drizzle/+bug/951788

henrik

On Tue, Apr 17, 2012 at 12:29 PM, Muhammad Waqas Iftikhar
<coldheartpks@xxxxxxxxx> wrote:
> Mr. Marcus can you please tell us which version of drizzle server are you
> running.
> We have been trying to solve the issues in those 12 tests.
> Issues :
>
> 3 tests in Cancel test files : implicit joins which is no longer allowed in
> drizzle as said by Sohair above. SOLVED
>
> Diver Test (TestException Div by zero) unable to detect drizzle running it
> always perceives MySQL running even though always connected to
> drizzle server. If we remove
> "if(getConnection().getMetaData().c.toLowerCase().equals("drizzle")" the
> test runs fine as the exception generated is correct "ExceptionDivByZero"
> though WORKED BY REMOVING IF CONDITION.
>
> primaryKeysTest(org.drizzle.jdbc.DatabaseMetadataTest)   NO COLUMN NAMED
> "COLUMN_KEY" FOUND
> exportedKeysTest(org.drizzle.jdbc.DatabaseMetadataTest) NO COLUMN NAMED
> "kcu.refernced" FOUND
> importedKeysTest(org.drizzle.jdbc.DatabaseMetadataTest) NO COLUMN NAMED
> "kcu.refernced" FOUND
> testGetTables(org.drizzle.jdbc.DatabaseMetadataTest)       NO COLUMN NAMED
> "table_comment" FOUND
> testGetTables2(org.drizzle.jdbc.DatabaseMetadataTest)     NO COLUMN NAMED
> "table_comment" FOUND
> testGetColumns(org.drizzle.jdbc.DatabaseMetadataTest)    NO COLUMN NAMED
> "table_type" FOUND
> dbmetaTest(org.drizzle.jdbc.DatabaseMetadataTest)           NO COLUMN NAMED
> "COLUMN_KEY" FOUND
>
> Sohair will upload the diff patch in few hours. Please do comment.
>
>
> On Wed, Apr 11, 2012 at 9:25 PM, Sohair Butt <buttsohair1@xxxxxxxxx> wrote:
>>
>> Solved the errors in CancelTest.java. The queries being used in the
>> functions involved implicit joins of the tables. This is no longer allowed
>> in Drizzle and generates an error. Using CROSS JOINs in place of implicit
>> joins in the queries solved the problem. For exmaple,
>>
>> ("select * from information_schema.columns CROSS JOIN
>> information_schema.tables CROSS JOIN information_schema.table_constraints")
>>
>> Also, Waqas and I will be having our Midterm exams during the next 3-4
>> days. We will try our best, though, to stay active during this time and
>> complete this task.
>
>
>
>
> --
> Regards Waqas
>
> _______________________________________________
> Mailing list: https://launchpad.net/~drizzle-discuss
> Post to     : drizzle-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~drizzle-discuss
> More help   : https://help.launchpad.net/ListHelp
>



-- 
henrik.ingo@xxxxxxxxxxxxx
+358-40-8211286 skype: henrik.ingo irc: hingo
www.openlife.cc

My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559


Follow ups

References