> I've spent considerable time trying to configure the built-in derby embeded
> as a CF client variable store and have failed utterly. It seems to be
It's not impossible. I followed through the gist of what you said you'd
tried, and it worked fine for me. This doesn't help you much, I know, but
it confirms it is possible. And confirms the source of your problems might
be a bit closer to where you're sitting than you suggest they might be ;-)
> I created the database, created the dsn, set the dsn as the client store and
> it all looked okay. But it isn't. The CLOCAL and CGLOBAL tables were not
> created as they should have been (and were for SQL Server).
Well it does actually *tell you* it won't create them automatically when
you go to set the DSN as the client store. I suppose one has to read what
it says on the screen, which I have to say I don't bother doing a lot of
the time in CFAdmin because I "know" what the text says. This very screen
has caught me out with that before. Just the first time, though.
> So I created them
> by hand as described in the
What were the exact statements you ran to create the tables & indexes?
> Changing various things yields different errors,
What are the error messages?
> 8,0,1,195765 standard). When I create an embedded derby dsn, I get the
> "default" [i]Data & Services > Datasources > Other[/i] screen. There's
> "derby" about it.
That sounds wrong. I get " Data & Services > Datasources > Apache Derby
Embedded" on all three servers I have at my disposal currently (a mix of
CF8 multiserver, CF8 stand-alone), and the rest of the screen is
Derby-specific. It sounds to me like your install is bung. Are you saying
when you select "Apache Derby Embedded" you just get the same screen you
would have had you selected "other"? Odd.
> So, frankly, it seems pretty pointless and useless to me.
Well, I suppose that's one way of looking at it. But quite a
counterproductive one, and one that's not likely to get you too far. It's
not CF's or Derby's fault something is bung with your install, is it?
> If someone can point
> me DIRECTLY to relevant information, I'd appreciate it.
You've got all the relevant info you need. The only variation to the
normal instructions for setting up a DSN for client variables is that one
has to create the relevant tables. And to do that, all I did was to copy
the script from that URL that has the table-create statements on it, and
change the Acccess-specific data-types to Derby-specific ones: memo->clob,
However if you're not getting the right screen when trying to add the DSN
in the first place, I think you'd better try to sort that out first.
> I cannot believe in the
> year plus this product has been out that NO ONE has done this,
I think your problem here is your attitude that because *you* can't make
something work then automatically nor can anyone else. That is seldom
going to be the case, surely (or you lead a very charmed life). I always
find that when something doesn't work for me in CF it's almost always my
> is one of the things you can do, yet there's nothing. Even searching for just
> "derby" on these forums yields only three hits, none of which are relevant.
Oh, the search on these forums is rubbish, so don't put too much stock in
that. You're better off using Google Groups to search these forums.
That said, if there's not much discussion on people having this sort of
problem, it's probably because they haven't *had* these problems. Which in
turn points even more towards the odds are that you're doing something
So... can you please clarify what you said about getting the "other" DSN
screen, and also clarify how you created the Derby DB, and what your
table-create statements were. Also what those errors are that you're
getting. Then we can work out how to get you sorted.