Doing it in my app means polling the other db instead of receive an
"interrupt" via trigger ... I can do it but it's the "polling vs interrupt"
...
Obviously I prefer to sit and wait for data instead of looping looking for
data but if it's the only way ...
--
[image: Just A Little Bit Of
Geekness]
On 4/23/08, Federico Granata <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 23, 2008 at 12:22 AM, Igor Tandetnik <[EMAIL PROTECTED]>
> wrote:
>
>
> > Each connection has its own independent temp database. You've created a
> > temporary trigger which exists in the temp database for your connection.
>
On Wed, Apr 23, 2008 at 12:22 AM, Igor Tandetnik <[EMAIL PROTECTED]>
wrote:
> Each connection has its own independent temp database. You've created a
> temporary trigger which exists in the temp database for your connection.
> The trigger simply doesn't exist on the other connection.
>
damn ...
Y
Federico Granata
<[EMAIL PROTECTED]> wrote:
> I have two db, the main one is used from mine sw (call this db A),
> the other is used from another sw (call this db B).
> I open A, attach B, create a temp trigger in A triggered by insert
> into a table in B and writing in a table in A
>
> If I insert
Hi, I hope this question isn't a noob one like my last one ...
I have two db, the main one is used from mine sw (call this db A), the other
is used from another sw (call this db B).
I open A, attach B, create a temp trigger in A triggered by insert into a
table in B and writing in a table in A
If
5 matches
Mail list logo