From: Christoph B. <be...@od...> - 2002-05-08 09:52:04
|
> > My preferred solution is to have a seperate LongStringType (and > LongBinaryType). If we could implement these types in a reasonably > platform-nuetral way, I would love to add them in as built-in types > ASAP. However, I have a funny feeling we would need to do special > things for some databases. The recommended approach at present is > to implement a custom type for your particular database. > I don't think, that separate types are what we need here. The problem here is, that these things are really dbms specific. The user should not have to change the mapping when switching to another dbms. That's why I think we should simply extend the mechanism of regestering type names. I made a patch, which I just submitted . > Its about time I had a closer look at the portability issues here. > If anyone else wants to take care of this, they are very welcome. > (I have a bit of a backlog of issues like this right at the moment.) > > Gavin > |