Making the switch from MySQL to PostgreSQL?
I’ve spent the last year becoming really comfortable with MySQL, but due to its increasing trendiness and my desire to homogenize my web-apps with Heroku, I’d like to start using PostgreSQL for my web apps instead. There are a resources out there for learning PostgreSQL, but I don’t really want to have database concepts explained to me from scratch again, and I don’t want to have to re-learn all the stuff that’s pretty much the same.
Breaking 1NF to model subset constraints. Does this sound sane?
My first question here. Appologize if it is in the wrong forum but this seems pretty conceptual. I am looking at doing something that goes against conventional wisdom and want to get some feedback as to whether this is totally insane or will result in problems, so critique away! I am on PostgreSQL 9.1 but may be moving to 9.2 for this part of this project.
Established coding standards for pl/pgsql code
I need to standardize coding practices for project that compromises, among others, of pl/pgsql database, that has some amount of nontrivial code.
Verify uniqueness of new content
I’m working on a review site, where there is a minor issue with almost duplicate reviews across items. Just a few words are changed. It would be very nice to be able to uncover these duplicates before they are approved by a moderator, and I’m hoping someone could chime in on the best strategy to get there.
Logging to database: Log first or action first?
Long story short, I’m working on a web-based frontend that interacts with a database, and one of the functions is that every action on a particular table gets logged to keep a full history of all changes to that table.
What are some database designs that support lineage tracing?
Environment PostgreSQL 9.1 Java Problem I’ll try to illustrate the problem here as simply as possible: I’m trying to record the following relationship: Node 1 => Node 2 => Node 3 Where Node 1 is the parent of Node 2, and Node 2 is the parent of Node 3. In the database table, the initial […]
Is it possible to develop a web application entirely in Javascript today (client and server) including a RESTful API exposing PostgreSQL data?
Where I work we have over a dozen internal SW systems that we have developed in-house using a variety of technologies, frameworks, and languages. Those include various from Microsoft (ASP.NET Web Forms, WebAPI, WinForms, SharePoint, Office Automation, Win8 Native Apps, SQL Server, SSRS) and others not from Microsoft (plain-old JS/HTML/CSS, PHP, Lithium, PostgreSQL, MySQL). Our SW dev team has grown and shrunk again to where it’s just me and one other dev now. I love trying shiny new tech and taking advantage of different tools to get things done, which partly explains the huge span of different technologies we’ve chosen over the years, but we’re suffering from the “jack of all trades, master of none” syndrome.
Suggestions designing an XML polling deamon in python
I’m about to take on a new project for a client designing a server-side python program that will poll a number of XML streams at regular intervals and populate a Postgresql database with results. The system will basically act as an XML cacheing daemon and populate a database. That database will then be accessed by a separate program which will serve that data in JSON to a public-facing website.
Suggestions designing an XML polling deamon in python
I’m about to take on a new project for a client designing a server-side python program that will poll a number of XML streams at regular intervals and populate a Postgresql database with results. The system will basically act as an XML cacheing daemon and populate a database. That database will then be accessed by a separate program which will serve that data in JSON to a public-facing website.
Suggestions designing an XML polling deamon in python
I’m about to take on a new project for a client designing a server-side python program that will poll a number of XML streams at regular intervals and populate a Postgresql database with results. The system will basically act as an XML cacheing daemon and populate a database. That database will then be accessed by a separate program which will serve that data in JSON to a public-facing website.