Hi Denins,
Dennis Bekkering wrote:
Hi,
I found out that the select IN problem had to do with different charsets on
the column level, since my id's where varchars this problem occured
suddenly
, i checked all column charset but couldn't find a difference between them.
The deeper i get into mysql the more i find out why not everybody likes
this
database that much. It is very hard to determine what is wrong and why.
What
are other developers favorite database either open source or not? Are there
databases that have meaningfull error messages anyway?
Regarding the GUID's and collections i tried another appraoch then i first
suggested. I added an xtra guid field to every table, now tables have a
local int id and a global varchar one. I did this to be able to move on but
it is better anyway i think. For collections (either 1:N or M:N) i only
send
the GUID's of the members in that collections. If the new records are send
before that then the collections can be assambled thereafter without having
to fall back on sql. The cache doesn't have to be cleared also. The last 2
years i tried several approaches but i think this one will actually work.
For me It is one of the hardest problems to find a solution for. Anyway i
had to browse the OJB source and that was fun, i discovered source files
regarding SODA. What is the status of this?
The SODA support is deprecated and will be removed.
http://db.apache.org/ojb/status.html
Think the current implementation is rudimentary.
I made a conceptual interface
implementation for SODA, the same interface that i use to query OJB, but if
OJB already supports SODA i would be crazy to build it myself. Can i for
instance use db4objects with OJB?
Sorry, nope! At the beginning of OJB some people plan to support beside
RDBMS and other persistence datastores, but it was too complex to
realize with a few OJB committer.
regards,
Armin
Cheers,
Dennis
2006/5/13, Dennis Bekkering <[EMAIL PROTECTED]>:
All,
I converted all my int id's and refs to varchar id's and ref's, i
offcourse updated the repository file also. Now it seems that OJB expects
id's to be of type int in 1:N and M:N relations. I get errors regarding
select where id IN (?,?,?,?,?). I did not really looked in the source
yet at
what is happening, so my questioin is if it is at all possible to use
varchars in 1:N and M:N relations. I can not post the log because i
have the
new stuff at home only right now and am at work (on saterday?, yes i am a
crazy nerd ;-). If it should be possible i will dive into it deeper
and try
to find what i am doing wrong.
Cheers,
Dennis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
