ecific version of the function a la
> git/svn...and then you could do diffs and what not so that you
> wouldn't have to rely on text files which get lost because they were
> on a tiny jump drive.
>
> Just my $1.70
>
>
>
> Regards,
>
> Rhys
>
x27;ll have to update the index for every single entry. And the trigger
> won't help either. Import into a single table and split it out into
> further tables after if required. And finally the constraint should
> probably be applied after too, so cull any violating rows after importing.
>
> Thom
--
Nagy Zoltan (kirk)
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
hi,
you should use something similar to 'merge sort'
but only if your input is sorted (m_bx expects this)
if your subjects (numbers) are not going beyond a certain limit eg(65535)
take up an array and filter
you can generate a poly for array B's roots, and calculate A's points
-where it's 0,
