Search Postgresql Archives

Re: Postgresql Development Options

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 06/04/15 08:46, Ray Madigan wrote:
The application will be very small, its main function is as a data acquision tool that reads data from an c api and does minimal processing and feeds it off to a postgresql database for offline processing. I haven't written the PC side application yet, just a prototype in Qt. It just hast to be as fast as possible, or I would java. I am comfortable with c++, but would use other language if it would get the job done.

The ui is used basically to control the device that is generating the data, and parsing it into sql to send to the database. Very simple.

Thank you.

ps, if I shouldn't include your email in my response tell me, I am not sure what the conventions are.

On Sun, Apr 5, 2015 at 1:35 PM, Adrian Klaver <adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>> wrote:

    On 04/05/2015 01:21 PM, Ray Madigan wrote:

        I have been using postgresql in java off and on for many
        years.   I now
        have an assignemtn where I have to build a very straight forward
        networked application that needs to be able to insert Array
        data types
        from a windows environment to a remote Linux Postgresql database.

        My first attempt was to use Qt.  Their is a postgresql driver
        and found
out the hard way that it doesn't support the Array data type. I need a
        small ui so the user can set options for the application.   My
        question
        is, are there other UI options that I can use to development this
        application.


    What languages are you comfortable with?

    Seems from the above the UI is separate from the application, is
    that the case?

    Is so what is the application written in?


        Thanks in advance.



-- Adrian Klaver
    adrian.klaver@xxxxxxxxxxx <mailto:adrian.klaver@xxxxxxxxxxx>


The convention is to bottom post (like I am here), and include as much of the previous emails as is relevant.

You don't have to be too strict in cutting things out of previous emails, it is more to prevent emails getting far too long - in the above case no real need to omit things.

In general mention what version of PostgreSQL you are using, though not really relevant here!


Cheers,
Gavin


--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux