Recommend a good db4o viewer

views:

543

answers:

+7 Q:

Recommend a good db4o viewer

I'm playing around with db4o, and I have the Object Manager viewer thingy for Visual Studio. It seems okay, but not exactly on par with tools like HeidiSQL/SQL Studio/etc., not to mention that it locks the db4o file--I can't use my db4o app and Object Manager at the same time.

Maybe I'm using it wrong, but regardless, I'd like to know what else is out there. What tools would you recommend for looking at and manipulating db4o files?

UPDATE: I've been using LINQPad. There is some yak-shaving involved, but it's working pretty well. It still leaves a lot to be desired in terms of the functionality available in applications like HeidiSQL/SQL Studio/etc., but it's a start.

+1 A:

Me too. I've been using DB4O for a few years, and have found the Object Manager clumsy, and often buggy (sometimes it won't open my large DB4O database at all).

I know of no alternatives, unfortunately.

Judah Himango 2010-03-09 18:21:31

Maybe we should write one then, if there really aren't any good alternatives?

mgroves 2010-03-09 18:31:02

Sounds good to me. Send me a patch for that. :-)

Judah Himango 2010-03-09 18:42:10

Sorry, when I said "we", I really meant "you" :-P

mgroves 2010-03-09 18:44:58

Yep, so when I read "we", I figured it meant "you", Mr. Groves. ;-)As for me, I've got my hands full at the moment.

Judah Himango 2010-03-09 19:01:00

Well, if I still don't hear of any alternatives, I'll eventually start a project, which you will be welcome to participate in should your hands get freed up :)

mgroves 2010-03-09 19:23:14

Fair enough. Email me if you start: judahgabriel at gmail

Judah Himango 2010-03-09 21:39:48

+5 A:

I suggest you use LINQPad as a first start.

Gamlor has a great tutorial on how to use LINQPad with db4o. You'll need to modify that a bit so you use client-server access (thus not locking your db).

I don't want to re-post his code here, because I think it's pointless and he's also a user here, don't wanna win his laurels.

For me, LINQPad seems to be the best approach, also because I can use it on my server, where I'd be having trouble with OME for obvious reasons.

mnemosyn 2010-03-10 13:33:53

I didn't even think about LINQPad in that context: good call.

mgroves 2010-03-10 14:29:25

Yes, LINQPad isn't a bad choice. But without the domain-classes (or in the Java world) it's useless. So the search for a excellent ad hoc query/diagnostic tool for db4o goes on.

Gamlor 2010-03-10 19:03:23

But is that really a common scenario? I mean, you typically will have the model binaries at hand, won't you?

mnemosyn 2010-03-10 20:31:28

Yes, you normally have the model binaries around. But would it be easier if you don't have to setup LINQPad?

Gamlor 2010-03-11 16:41:36

Yeah it would be. Do you know of something that does that? :)

mgroves 2010-03-11 18:10:39

+2 A:

Hi,

We have discussed integrating some kind of "interactive LINQ query" into Object Manager (.Net of course :).

If you think this would be a nice feature, please vote in the issue here.

Also, any input on how to improve Object Manager is welcome.

Vagaus 2010-03-17 11:48:08

Sounds like a good idea. Maybe a LINQPad plugin would be easier? Also, what about locking the db4o file when using OM? That can be very frustrating.

mgroves 2010-03-17 12:59:07

Not locking the file can lead to database corruption. The solution (IMHO) is to use it in C/S mode (but your app needs to use the same mode of course)Regarding a LINQPad plugin it may have some potential issues (for instance licensing). To be honest, I am not used to LINQPad.

Vagaus 2010-03-17 14:21:40

ansaurus

tags:

views:

answers:

Recommend a good db4o viewer

related questions