| From: | John DeSoi <desoi(at)pgedit(dot)com> |
|---|---|
| To: | Theodore H(dot) Smith <delete(at)elfdata(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Why can't I connect to postgres? |
| Date: | 2006-07-24 17:28:30 |
| Message-ID: | 6C98F656-1326-469E-AE9E-D1C4CA873AE3@pgedit.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jul 24, 2006, at 12:57 PM, Theodore H. Smith wrote:
> Well I tried NaviCat and some others, they seem to work. Perhaps
> the problem was with REALbasic.
I don't know the details of REALBasic, but perhaps it uses ODBC or
some other "generic" connection method. In this case, you probably
have to do some additional setup and configuration.
>
> I can connect via perl, also, which is good.
>
> What's a good way to store the database logic?
>
> Say for example, I want to do something to the database, can I just
> say something like DataBasePleaseTryRegisterUser( "name",
> "details", "serial", "etc" ); where DataBasePleaseTryRegisterUser
> would be some kind of function stored in the database itself?
>
> Or should I put the logic into my perl files? And treat the
> database as just that, a blind database which can store invalid data.
PostgreSQL has excellent stored procedure/function support. I prefer
to use that whenever possible. The starting points are CREATE
FUNCTION and pl/pgsql:
http://www.postgresql.org/docs/8.1/interactive/sql-createfunction.html
http://www.postgresql.org/docs/8.1/interactive/plpgsql.html
John DeSoi, Ph.D.
http://pgedit.com/
Power Tools for PostgreSQL
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schiltknecht | 2006-07-24 17:49:03 | Re: unknown error message |
| Previous Message | Raymond O'Donnell | 2006-07-24 17:28:12 | Re: Why can't I connect to postgres? |