Hi Tim,
The only problem with the pbxt database was that you could not drop it.
I have fixed that problem now.
So now, if you have no more PBXT tables, you can drop the pbxt
database (if you still have PBXT tables, you get an error on drop).
And, if the pbxt database does not exist, it is automatically created
when the first PBXT table is created.
On Oct 2, 2008, at 3:11 PM, Tim Soderstrom wrote:
Shame on me for posting when I'm not actually a real developer :)
But I did have a question I hope people don't mind I ask anyway. On
the vein of PBXT - currently, it stores global files in the 'pbxt'
sub-directory off of the datadir (at least it does with MySQL 5.1).
Which works fine, but it does create a 'pbxt' database (since MySQL
thinks directories are databases). I could see more engines
potentially using this approach, so is anyone looking at tackling
this for Drizzle? Of course, fixing that in MySQL would be nice too,
but it seems like Drizzle likes PBXT a lot more than MySQL does :)
Tim
On Oct 2, 2008, at 2:10 AM, Paul McCullagh wrote:
Hi Stewart,
I have started the work already. I am taking every change back into
PBXT, so that I have one source code base for MySQL 5.1, 6.0 and
Drizzle. So far so good...
If you pull the drizzle trunk (which compiles on Mac) into
lp:~stewart-flamingspork/drizzle/pbxt, then I will merge back when
I am done.
On Oct 2, 2008, at 8:40 AM, Stewart Smith wrote:
On Thu, Sep 25, 2008 at 11:14:56PM +0200, Paul McCullagh wrote:
Ahm... that was quick!
:) See what a 6+hr layover in frankfurt will do :)
I'm still trying to get PBXT to run with the latest 6.0 version,
and I
think I started at about the same time you did...
It's probably useful to go through each of the patches there and
re-do
some of the work. A bunch of the compiler warnings I solved in
rather
silly ways. e.g. unused parameters, i just did (void)foo; instead
of the
better solution of removing the parameter.
I'm OK with this solution for the moment. Some of these cannot be
changed because they involve callbacks which sometimes/may use the
parameters.
I think there may be some real bugs in some of the signed vs
unsigned
warnings/typecasts that possibly only show up with logs (or
others) at >
2 or 4GB.
Yes, I noticed this, and have changed the solution in some cases.
In particular, when off_t and size_t are involved, then we have to
cast all to off_t, because I assume off_t >= size_t (I am also
using size_t instead of ssize_t).
Best regards,
Paul
--
Paul McCullagh
PrimeBase Technologies
www.primebase.org
www.blobstreaming.org
pbxt.blogspot.com
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
--
Paul McCullagh
PrimeBase Technologies
www.primebase.org
www.blobstreaming.org
pbxt.blogspot.com
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
