Bs and BLOBs
in a separate table and referencing them by rowid is what
I do.
I've had good luck with putting large texts into their own files, and
storing the file names in the tables. But that precludes searches
within the texts themselves. My applications didn't need to do t
not inside of the database manager. :)
But should I change my mind, I'm gonna bookmark your email just in case!
b.g.
--
Bill Gatliff
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
es
where I know I'm going to use a SQL statement only once...
b.g.
--
Bill Gatliff
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
uld otherwise be the ideal solution because then I _could_
use select(2) et al. Right now, though, the schemas are designed to
meet the needs of the system as a whole; the GUI has to take what's
left. :)
b.g.
--
Bill Gatliff
[EMAIL PROTECTED]
---
Trevor Talbot wrote:
On 10/31/07, Bill Gatliff <[EMAIL PROTECTED]> wrote:
I prefer not to poll for changes, because the system is
performance-constrained. So instead, I'm using an AFTER UPDATE trigger
in the data-generating process to launch a C function that posts to a
semaphor
getting unblocked? Am I missing an entirely different---
and better--- way of synchronizing my GUI to the database?
Thanks!
b.g.
--
Bill Gatliff
[EMAIL PROTECTED]
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
6 matches
Mail list logo