Adam Brusselback wrote:
> I appreciate the response Tom, and you are correct that the workaround would
> not work in my case.
>
> So no index expressions can return the their value without recomputing
> without that work around? I
> learn something new every day it seems.
> Thank you for the al
I appreciate the response Tom, and you are correct that the workaround
would not work in my case.
So no index expressions can return the their value without recomputing
without that work around? I learn something new every day it seems.
Thank you for the alternate method.
-Adam
On Wed, Nov 25,
Main reason I was hoping to not do that, is the value that would be stored
in that column is dependent on what is stored in the attachment_bytes
column, so to be 100% sure it's correct, you'd need that column controlled
by a trigger, disallowing any explicit inserts or updates to the value.
Was hav
Adam Brusselback writes:
> CREATE TABLE attachment
> (
> attachment_id uuid NOT NULL DEFAULT gen_random_uuid(),
> attachment_name character varying NOT NULL,
> attachment_bytes_size integer NOT NULL,
> attachment_bytes bytea NOT NULL,
> CONSTRAINT attachment_pkey PRIMARY KEY (attachment_
On Wednesday, November 25, 2015, Adam Brusselback
wrote:
> Hey all,
>
> I have an attachment table in my database which stores a file in a bytea
> column, the file name, and the size of the file.
>
> Schema:
> CREATE TABLE attachment
> (
> attachment_id uuid NOT NULL DEFAULT gen_random_uuid(),
Hey all,
I have an attachment table in my database which stores a file in a bytea
column, the file name, and the size of the file.
Schema:
CREATE TABLE attachment
(
attachment_id uuid NOT NULL DEFAULT gen_random_uuid(),
attachment_name character varying NOT NULL,
attachment_bytes_size integ
