Search Results

Search found 7 results on 1 pages for 'enterprisedb'.

Page 1/1 | 1 

  • PostgreSQL / Ruby for commercial application

    - by RPK
    I am planning a web-based commercial application with front-end RoR and back-end PostgreSQL. I've some confusion about RoR and PostgreSQL Edition to use. For RoR, I have Aptana RADRails installed. For PostgreSQL, a free variant is also available at EnterpriseDB. Previously I installed a free EnterpriseDB PostgreSQL variant and it was very smooth and had professional touch. It was quite different from the one available from PostgreSQL website. I want to know which IDE and RoR variant to use for my project. I have no idea of Ruby and Rails. I will be learning and developing simultaneously. Also, which PostgreSQL variant to use? Can these two technologies be used for a developing a commercial application?

    Read the article

  • No getdate() function in Enterprise PostgreSQL

    - by Suezy
    Hi guys, do you have any idea on how to have getdate() function in enterprise postgresql? I upgraded to EDB-PSQL, and now when I tried to restore old data from the free PSQL, it returns error on some tables since there is no getdate(). I believe this should automatically be created upon creating new database? But it didn't. :( Only now() function. Can I create the function instead? Help!

    Read the article

  • Is it possible to upgrade from Postgres 8.3.3 with existing databases to 8.4.2 (installed windows vi

    - by WildWezyr
    I'm considering upgrade from Postgres 8.3.3 to 8.4.2 on my machine (it has Windows Vista). Windows Installer (one click installer) for Postgres 8.4.2 that can be downloaded from enterprisedb.com offers only fresh install (it does not recognizes my current installation of v8.3.3). Is it possible to upgrade with all existing databases converted and visible (automatically migrated?) in new version just after upgrade? Or I have to do something more - backup/restore all my databases manually?

    Read the article

  • What steps should be taken to ensure that an open source database gets ready for production?

    - by I_like_traffic_lights
    I am considering using GridSQL in a production environment. However, I do have some indications that it is not ready. One is that it got excluded by the offering of EnterpriseDB a while ago, and the forums seem to report a few wrong results and relatively severe bugs. The alternatives to GridSQL, however cost around 100.000$ to buy, so I was thinking to utilize some of this money to ensure that GridSQL gets ready for production. At the same time, I could risk spending 50.000$ and months of work on the development of GridSQL, just to discover that the design was flawed and that a complete rewrite is needed. Then I would have to buy the commercial alternatives to GridSQL and the existence of my startup would be at risk. Question What steps would you take to ensure that there is as little risk as possible that the worst case scenario described above would happen? It is unrealistic that I could do much testing nor code review/coding myself (I am also not the best developer), so please describe where to find the guys that would need to do the work.

    Read the article

  • Daemons did not start automatically ubuntu 10.04

    - by Anton Prokofiev
    Hello, All! I have a strange behavior on Ubuntu 10.4: few daemons (apache2 and postgresql (8.4SS from enterpriseDB) did not start automatically. Funny things that time-to-to they do. (If I just restart my computer everything looks ok, but if I turn it off for the night, nothing work..., so I have to start them manually) I've googled this problem a little bit, but the only answer I have found was to run: sudo update-rc.d apache2 defaults I've called it but the answer was: System start/stop links for /etc/init.d/apache2 already exist. Any Ideas?

    Read the article

  • Remove postgres from Mac - installed in /usr/local/, can I just delete files?

    - by Richard
    I want to completely uninstall postgres and start from scratch - the version I have is refusing to work with PostGIS 2.0. I have read other answers on how to do this, but none of them seem to fit the way postgres is set up on this machine. I'm not sure postgres was originally installed on this machine - it wasn't via brew or Postgres.app or the EnterpriseDB installer - but it seems to be living in /usr/local: $ which psql /usr/local/pgsql-9.1/bin/psql The postgres binary itself is in /usr/local/var/postgres/. How can I kill it forever? Can I simply go to /usr/local and do rm -rf pgsql-9.1, and the same in /usr/local/var, and make sure there are no paths in my profile file? Or is there more to it than that? From memory I think I'll need to delete the database files too somehow. Thanks for the help.

    Read the article

1