Hi John,
Thanks for your useful info. I really apprecaite it. I got this problem when the SAS application try to install the scoring model. So I am very confused.
> 1) What's the info in .dll/.so ?
thats the binary code compiled and linked from C, windows calls this
DLL (Dynamic Link Library), while unix usually calls it SO (Shared
Object). Mac OSX has yet another name (dylib or something).
thats the binary code compiled and linked from C, windows calls this
DLL (Dynamic Link Library), while unix usually calls it SO (Shared
Object). Mac OSX has yet another name (dylib or something).
---- Grace comments : this need the superuser privileges on the server to copy those .so ( we are on the linux server) to the postgresql server ?
correct ????
> 2) .sql scrap is the binary installation file?
the .sql is the CREATE FUNCTION statement mostly.
--- Grace comments : we already grant create privileges on the saslib schema. So it means they can this scrap by themselves ???
> 3) For the same database, we need update C functions frequently ?
you tell me? how often do your programmers change them?
---- Grace commends : they tried to SAS to create lot of models. So I amn't sure about this issues. But John, thanks a lot for your answers.
the .sql is the CREATE FUNCTION statement mostly.
--- Grace comments : we already grant create privileges on the saslib schema. So it means they can this scrap by themselves ???
> 3) For the same database, we need update C functions frequently ?
you tell me? how often do your programmers change them?
---- Grace commends : they tried to SAS to create lot of models. So I amn't sure about this issues. But John, thanks a lot for your answers.
Thanks.
Regards.
Grace
On 06/12/12 12:22 PM, leaf_yxj wrote:
> 1) What's the info in .dll/.so ?
thats the binary code compiled and linked from C, windows calls this
DLL (Dynamic Link Library), while unix usually calls it SO (Shared
Object). Mac OSX has yet another name (dylib or something).
> 2) .sql scrap is the binary installation file?
the .sql is the CREATE FUNCTION statement mostly.
> 3) For the same database, we need update C functions frequently ?
you tell me? how often do your programmers change them?
--
john r pierce N 37, W 122
santa cruz ca mid-left coast
--
Sent via pgsql-general mailing list ([hidden email])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
If you reply to this email, your message will be added to the discussion below:http://postgresql.1045698.n5.nabble.com/How-to-create-c-language-in-postgresql-database-Thanks-tp5712221p5712261.html
View this message in context: Re:Re: How to create c language in postgresql database. Thanks.
Sent from the PostgreSQL - general mailing list archive at Nabble.com.
