Andrus, As a C# developer myself, I'd recommend learning pl/pg sql for writring stored procs. It's designed specifically for the kinds of iterations and other operations you need when hanlding a recordset. It's nothing like transact-sql of SQL Server. If you must have full C# integration, then you're better off with SQL Server 2005. By the way, .NET LINQ will make most of your current thinking irrelevant in about 12 months. On 4/2/07, Andrus <kobruleht2@xxxxxx> wrote:
Last change for this project was 3 years ago. So I think that it is dead. I'm writing application in C#. I expected that I can wrote stored procedures in C# also using something like mod_mono in Apache. So it seems that most reasonable way is to learn dreaded plpgsql language and write stored procedures in it. Andrus. >> Any idea how to write server-side stored procedures in C# for >> PostgreSQL database ? > > There's an old project called PL/Mono > <http://gborg.postgresql.org/project/plmono/projdisplay.php>, but as > far as I know it's unmaintained. You might want to try to contact the > author. :) > > Cheers, > David. > >> In windows .NET 2 framework should be used and in Linuc/Mac/Windows >> MONO should be used for this. >> >> How to install MONO engine as server-side language to PostgreSQL ? >> >> How to call .NET dlls from PostgreSQL stored procedure ? > >> >> Andrus. >> >> >> ---------------------------(end of broadcast)--------------------------- >> TIP 1: if posting/reading through Usenet, please send an appropriate >> subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your >> message can get through to the mailing list cleanly > > -- > David Fetter <david@xxxxxxxxxx> http://fetter.org/ > phone: +1 415 235 3778 AIM: dfetter666 > Skype: davidfetter > > Remember to vote! > Consider donating to PostgreSQL: http://www.postgresql.org/about/donate > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
