> > I would argue that S3 is *the* standard for cloud based storage.
>
> It isn't really. It is only if you're using AWS (and yes, I know other
> cloud vendors offer 'compatible' APIs). I don't see it as something that
> belongs in core Firebird. It is something that can be done in a UDR, so
>
On 27-6-2019 19:11, Leyne, Sean wrote:
About S3, it's a non-standard product and certainly Firebird should not support
it
builtin.
I would argue that S3 is *the* standard for cloud based storage.
It isn't really. It is only if you're using AWS (and yes, I know other
cloud vendors offer 'c
> About S3, it's a non-standard product and certainly Firebird should not
> support it
> builtin.
I would argue that S3 is *the* standard for cloud based storage.
Sean
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
On 27/06/2019 13:42, Dimitry Sibiryakov wrote:
> 27.06.2019 18:38, Adriano dos Santos Fernandes wrote:
>> It's certainly already possible with UDR or UDF, so seems out of scope
>> for the system package.
>
> Oracle has different opinion:
> https://docs.oracle.com/database/121/ARPLS/d_lob.htm
>
>
On 27.06.2019 19:48, Mark Rotteveel wrote:
P.S. These are use cases where UDF-like functionality is required --
how else would someone provide this functionality? (I don't see UDRs
supporting this)
If you think a UDF can do it, why do you think a UDR wouldn't be able
to do it? UDRs can do m
On 27-6-2019 18:31, Leyne, Sean wrote:
RDB$BLOB_UTIL will have procedures and functions so blobs could be created,
opened, read in chunks, written in chunks, discarded (cancel).
What about functions:
- to read from/write to local disk*
That would require tight access controls, because just g
27.06.2019 18:38, Adriano dos Santos Fernandes wrote:
It's certainly already possible with UDR or UDF, so seems out of scope
for the system package.
Oracle has different opinion:
https://docs.oracle.com/database/121/ARPLS/d_lob.htm
It is better to have all routines in one package than swa
On 27/06/2019 13:31, Leyne, Sean wrote:
>
>> RDB$BLOB_UTIL will have procedures and functions so blobs could be created,
>> opened, read in chunks, written in chunks, discarded (cancel).
> What about functions:
>
> - to read from/write to local disk*
>
> - to read from/write to any external source
> RDB$BLOB_UTIL will have procedures and functions so blobs could be created,
> opened, read in chunks, written in chunks, discarded (cancel).
What about functions:
- to read from/write to local disk*
- to read from/write to any external source (Thinking of S3 compatible storage)*
Sean
P.S
27.06.2019 18:09, Adriano dos Santos Fernandes wrote:
Here a small example of how it could be used for writing data in chunks
Isn't one function to create a blob in temporary space enough instead of all
this?
For example:
execute block returns (b blob)
as
begin
b = DBMS_LOB.CreateTemp
Hi!
Working with BLOBs in PSQL is currently easy (substring, concatenate,
etc), but it's limited and sometimes very expensive.
If you concatenate a blob in a loop database grows a lot as intermediary
blobs are created and we can't even manually choose database/temp page
space.
I propose system p
11 matches
Mail list logo
