> Hello dev team,
> we are porting the MySQL Midgard interface to Oracle8.
>
> 1. Datatype
>
> With MySQL we use the TEXT datatype.
> With Oracle, there is:
> * VARCHAR2 with 4Kb searchable
> * LONG with 4 Mb no searchable
> * LOB with 4Gb no searchable
>
> We choose the LONG datatype. No objection?
I think it would be OK. Search will be implemented using external search engine
anyway.
> 2. Article extension
>
> We want also to have external tables to be linked to articles.
> Some local developpers ask me about this.
> Is this interface skeleton exists and frozen in V2?
It exists but IMHO database structure not frozen yet as we have to add some fields to
generic table's fields (like language code id). You can get it from
CVS (midgard-2.0 branch).
> We want also the article extension to be searchable.
> Before starting this point, any ideas are welcome.
We decided to create new set of functions mgd_get_custom_xxx() which will do such work.
> 3. Date datatype and functions
>
> Midgard uses a lot of mysql date functions and features.
> It's hard to implement in Oracle, this takes more time than expected.
> In the next release V2, what is the direction for the sql syntax?
Jukka is very busy for the moment but he is responsible how SQL connections will be
implemented. You may try to ask him directly.
> 4. First Beta release
>
> A first package based on Midgard 1.2.5 is expected
> February, 15th.
It would be good to integrate Oracle support into upcoming Midgard 1.2.6.
Could you fetch prerelease tar-balls from http://www.midgard.f2s.com/ and do patches?
Then I'll integrate Oracle wupport into main branch.
Sincerely yours,
Alexander Bokovoy.
---------------------------------------------
This message was sent via BSPU MailMan server.
http://www.bspu.unibel.by/MailMan/
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
