5
Vote

Sufficient setup allowing to create modules with support for third part DB systems (including Oracle) without need to modify Orchards source code.

description

Right now, the problem is that for some DB (e.g.: Oracle) is not possible to create DB access module without modifying Orchard source code. Issue includes column names generation, data types etc.
For details see http://orchard.codeplex.com/discussions/401440.

comments

BertrandLeRoy wrote Apr 11, 2013 at 3:05 AM

This was discussed at the last community meeting. Sébastien said that it wasn't worth the effort, seeing that there are relatively few databases that are compatible with nHibernate and that we don't yet support.

Can you elaborate on "column names generation, data types etc."?

gkumik wrote Apr 11, 2013 at 3:47 PM

For detail about column names, data types etc. Please see comment by slimjack (Edited Jan 16 at 2:45 PM) in http://orchard.codeplex.com/discussions/401440. It explain all steps. Generally Sebastien is right, there are only a few DB compatible with nHibernate and not supported by Orchard but Oracle DB is super important DB in some environments.

BertrandLeRoy wrote Apr 12, 2013 at 1:42 AM

Mmmh, I kind of stopped reading at "Oracle identifiers are restricted at 30 characters". Seriously? That sounds ludicrous. They are selling that? ;)

BertrandLeRoy wrote Apr 12, 2013 at 1:46 AM

Seems like there are workarounds for that 30 char limit...

Anyway, seems like Oracle compatibility should be done by someone who needs it (that's true of pretty much everything), especially as there are non-trivial hurdles.