[prev in list] [next in list] [prev in thread] [next in thread] 

List:       twig-devel
Subject:    Re: [twig-devel] files modul / virtual disc
From:       Jorma Tuomainen <webmaster () wizactive ! com>
Date:       2002-09-18 9:26:39
[Download RAW message or body]

Ok. I'll wait for 2.8 versions then. My boss was just asking this kind of 
feature.

- JT

On Wednesday 18 September 2002 10:27, Aaron Stone wrote:
> I added functions to the DB abstraction layer for handling BLOBs, they've
> been there for quite some time now, but there isn't any code using them
> yet. The test application was going to be Notes, which would receive the
> ability to store an attachment along with a text note. That code is 99%
> complete, but I have not committed it, I'm waiting for the 2.8 cycle.
>
> Aaron
>
> On Mon, 16 Sep 2002, Jorma Tuomainen wrote:
> > Do you have planned feature like this?
> >
> > I kinda have this kind of thing in my todo list but I really would need
> > some comments about "the best way(tm)" to implement this.
> >
> > I have thought some files table which would hold a file/row and it would
> > also keep groupid and stuff so this could be mainly used by groups
> > sharing .doc's and files like that.
> >
> > So table layout could be copied mostly from contacts like the code which
> > would have security ready so ppl that dont belong to group couldnt read
> > those files as they cant read contacts. Same would apply to ppl that
> > belong to some group but only have limited rights.
> >
> > That would definitely need blob field in table. It is easy to implement
> > for mysql but how about rest of the databases... IIRC Postges has some
> > funny way to handle blob's, you need to know OID for row and then put
> > LargeObject there... ADODB has nice way to handle this but since TWIG has
> > own db abstraction that is not possible.
> >
> > But please post your ideas so I can start developing this within week or
> > two. --
> > Jorma Tuomainen :: jt@wizactive.com :: http://wizactive.com/

[prev in list] [next in list] [prev in thread] [next in thread]