Yes, that'll work, but use MetaDataProtocol.MIN_SYSTEM_TABLE_TIMESTAMP to
ensure that you see the latest SYSTEM.CATALOG table.
On Thu, May 29, 2014 at 10:01 AM, Gabriel Reid
wrote:
> Thanks for the info James. Indeed, it makes sense (once you know it).
>
> @Dan The idea of having two separate p
Thanks for the info James. Indeed, it makes sense (once you know it).
@Dan The idea of having two separate points in time sounds
interesting, but I I think you're also right that it might be getting
pretty close to being overly complicated.
@James Any idea on how much impact it would have if tabl
Does it make sense to potentially have an option for Table Metadata to be
read at TS1 and the data to be read at TS2 or is that just too complicated
as a user interface?
-Dan
On Mon, May 26, 2014 at 5:49 PM, James Taylor wrote:
> Hi Gabriel,
> Yes, this is all WAD. We correlate the timestamp of
Hi Gabriel,
Yes, this is all WAD. We correlate the timestamp of table creation and
alteration with the connection timestamp so that you can see the schema as
it was at that point in time. That's what the data would match against (and
is validated against) as well. So, yes, table metadata is essenti
Hi,
I've been trying out the CurrentSCN connection parameter recently, and
it's behavior wasn't quite what I expected. I'd like to double-check
that the current behavior is in accordance with other people's
expectations, and if it isn't then I'll work on updating it.
There are two main issues I'm
