As an example of a filesystem access that is transaction dependent:
When I create a new supplier in the database, I need a set of
directories built on the file system.
If the directories are not there, it will cause a lot of problems when
dealing with this supplier.
When creating the supplier, I us
>> Is there any good reason not to include this functionality directly in
>> the database? (Too much parallel processing, engine not equipped for
>> that kind of processing, threading issues...)
>>
>>
> there are some issues still
>
> * missing integrated scheduler
> * missing autonomous tran
On 6/1/2010 11:12 AM, Szymon Guz wrote:
>
>
> 2010/6/1 Sim Zacks mailto:s...@compulab.co.il>>
>
> PG 8.2
>
> I am using plpythonu to add application server functionality to my
> postgresql database.
>
> For example, I have triggers and functions that FTP files, sends
> email,
2010/6/1 Sim Zacks :
> PG 8.2
>
> I am using plpythonu to add application server functionality to my
> postgresql database.
>
> For example, I have triggers and functions that FTP files, sends email,
> processes files, etc..
>
>
> Is there any good reason not to include this functionality directly
2010/6/1 Sim Zacks
> PG 8.2
>
> I am using plpythonu to add application server functionality to my
> postgresql database.
>
> For example, I have triggers and functions that FTP files, sends email,
> processes files, etc..
>
>
> Is there any good reason not to include this functionality directly
