[nem-en] SQL macros (dataSqlClient.n)

Kamil Skalski kamil.skalski at gmail.com
Sat Oct 21 10:41:55 CEST 2006


Ok, so probably the best way is to make the Helper module encapsulate
all the DB access during compile-time. If it used the
Mono.Data.SqlCharp, then we could have the single macro library
generating code for various DB providers.

On 10/21/06, Ildar Mulyukov <ildar at users.sourceforge.net> wrote:
> On 18.10.2006 15:37:05, Kamil Skalski wrote:
> >  And for the compile-time execution I cannot see other choices than
> > using reflection to instantiate provider specific objects and having
> > the customized implementation of stuff, where providers differ
> > between  each other in some helper classes. Making this
> > provider-independent  seems very hard and not worth the effort though.
>
>         Hi!
> I've found one nice library, that already implements the reflection for
> databases. It is Mono.Data.SqlSharp.DatabaseBrowser.dll from the
> SqlSharpGtk project:
> http://forge.novell.com/modules/xfmod/project/?sqlsharpgtk
>
> Another code example is in Mono tree itself, called SQL#:
> mono-1.1.17.2/mcs/tools/sqlsharp ,
> though this one is just a standalone application.
>
> IMO it's worthy to redesign dataSqlClient.n to use
> Mono.Data.SqlSharp.DatabaseBrowser.dll and have a ready-to-use database
> independent Macro.
>
> Regards, Ildar.
> --
> Ildar  Mulyukov,  free SW designer/programmer
> ================================================
> email: ildar at users.sourceforge.net
> projects: http://os-development.sourceforge.net/
> home: http://tuganger.narod.ru/
> ALT Linux Sisyphus
> ================================================
>
> _______________________________________________
> https://nemerle.org/mailman/listinfo/devel-en
>


-- 
Kamil Skalski
http://nazgul.omega.pl



More information about the devel-en mailing list