lidavidm commented on issue #3449: URL: https://github.com/apache/arrow-adbc/issues/3449#issuecomment-3322145200
> What about namespacing the type name in the value instead like ADBC:typename = $VENDOR_$TYPE_NAME? I'm not a fan of putting the namespace in the value because that introduces additional parsing and potential ambiguity. I think if we're going to go that way, we'd just want a single field like `ADBC:vendor_metadata` that contains a JSON blob or something (and I'd still rather not do that because that's less readable and more annoying to work with). I do agree with Curt that it feels a little unnecessary to do this extra namespacing. I would think it's a given that the type name is vendor-specific (even just the question of whether you should expect INT vs INTEGER vs INT4 vs...). There's nothing stopping applications from just searching for a key that ends in `typename`. (And note that the current drivers only add the namespacing because there isn't a standard for it.) Ultimately I'm not going to -1 this though given everyone else seems to have taken this as a base assumption. If we're doing this I would prefer `SNOWFLAKE:type` over `ADBC:SNOWFLAKE:type` given the contents at that point really have nothing to do with ADBC. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
