Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • What about InnoDB? How PostgreSQL integrates with VS? I tried a sample app, but pgsql's .NET connector has poor performance. Also PGSQL help is not easy if you stuck with VS and pgsql. Commented Jul 20, 2011 at 9:48
  • InnoDB solves some of the issues, but not all; as soon as you mix MyISAM and InnoDB, you practically lose transactions and referential integrity. Other than that, InnoDB is the way to go if you have to use MySQL. Commented Jul 20, 2011 at 14:21
  • Postgresql probably integrates with VisualStudio as badly as MySQL does, but at least you get a properly functioning database. Anyway, if you're going to use ASP.NET, might as well go all the way. Commented Jul 20, 2011 at 14:22
  • +1 for the .NET dll imports and CLR integration! When done properly, this can make SQL Server extremely powerful/flexible! Commented Jul 20, 2011 at 15:07
  • I am using InnoDB and till date, no problems. MySQL's .NET Connector works well. It is well optimized for better performance. I do look forward to use PGSQL but unavailability of a mature .NET Connector, sets me back. Commented Jul 22, 2011 at 19:04