Hi
Dne Thu, 2 Jun 2011 14:41:37 +0200 Tyron Madlener tyronx@gmail.com napsal(a):
Looking at the current way drizzle support is being implemented, it seems like it's going to be made with a PMA_DRIZZLE constant and a lot of if()'s all over pmas codebase. That sounds somehow messy to me. Isn't there a way with some git branching magic + regularly merging back or "preprocessor" (the conversion scripts before releasing pma, like its done with pootle) directives to keep those things seperate?
I'd rather prefer if all these things would be hidden somewhere in DBI and not exposed to other code.
Looking at the significant differences between MySQL and Drizzles this seems like a non-trivial change on pmas codebase. I don't know how the typical use cases are but I don't think a typical user will require phpmyadmin to be able to switch between MySQL and Drizzle. So what about releasing a drizzle supporting version of pma seperate from the mysql supporting version?
Well the Drizzle support is from beginning mostly to explore possibilities and see if it manageable to include it within our codebase or not, depending how much changes will be needed.