1. document how you did it 2. clean up how it is set up now, maybe make it possible to define the host to connect to from the command line
/Marcus On Tue, Apr 3, 2012 at 3:19 PM, Waqas Iftikhar <coldheart...@gmail.com>wrote: > Mr. Marcus we have run the test suite successfully. Can you please > elaborate on the second part of the exercise you suggested i.e "Cleaning up > that process to make it easier to get started". What are you referring to? > > > On Mon, Apr 2, 2012 at 10:49 PM, Henrik Ingo <henrik.i...@avoinelama.fi>wrote: > >> Hi Waqas, Sohair >> >> I saw that you posted a bug fix but didn't have time to look at it >> yet. Since this is not a project I will be mentoring I will probably >> pass reviewing it onto someone else, but publishing a bug fix >> certainly helps with your application. >> >> henrik >> >> On Mon, Apr 2, 2012 at 4:22 PM, Waqas Iftikhar <coldheart...@gmail.com> >> wrote: >> > We have sent you a private email >> > Mr. Marcus in that email we described our idea of how client side will >> work. >> > We have build jdbc of drizzle from source now can you please recommend >> any >> > bug or exercise in code of jdbc. >> > Mr. Ingo we have also attached our findings after reading the code of >> MySQL >> > 5.6 memcached implementation which you suggested us to do and also >> uploaded >> > the branch of garbage value return in multiplication and division in >> > drizzle. >> > Now can you suggest us another bug or exercise which would help getting >> more >> > knowledge on drizzle? >> > >> > >> > On Sat, Mar 31, 2012 at 4:19 AM, Sohair Butt <buttsoha...@gmail.com> >> wrote: >> >> >> >> Hello! >> >> Bug# 20093 of MySQL which we also found to be present in Drizzle has >> been >> >> solved. We've uploaded a branch that includes the fix. Here is the >> link to >> >> the diff: >> >> >> >> >> >> >> http://bazaar.launchpad.net/~team-serc/drizzle/fix-mysqlbug20093-garbage-return-value/revision/2 >> >> >> >> >> >> On Thu, Mar 29, 2012 at 6:21 PM, Marcus Eriksson <krum...@gmail.com> >> >> wrote: >> >>> >> >>> >> >>> my initial idea was to first execute the query "for real" once against >> >>> the server since that provides us with a lot of metadata about the >> result >> >>> set (data types etc), then be able to cache that metadata, and start >> >>> executing the query using a key-value lookup. >> >>> >> >>> i will write a more elaborate project proposal soon >> >>> >> >>> /Marcus >> >> >> >> >> >> Please do elaborate. But basically, the idea we've got from what you've >> >> said is that initially we'll execute the query by passing it through >> the SQL >> >> layer, gathering table metadata and caching it in the process. Later >> on, >> >> when a similar query comes along again, we'll see if the metadata >> cached is >> >> applicable. If it is, we just make a key-value look-up and then >> structure >> >> the result according to the cached metadata. Are we on the right track? >> >> >> > >> > >> > >> > -- >> > Regards Waqas >> >> >> >> -- >> henrik.i...@avoinelama.fi >> +358-40-8211286 skype: henrik.ingo irc: hingo >> www.openlife.cc >> >> My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 >> > > > > -- > Regards Waqas >
_______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
