-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…
-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…
-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…
-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…
-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…
-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…
-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…
-
Conceptually, it seems like it should be possible to create an `odo.resource()` from an in-memory object, like a `DataFrame`, for instance. I get an exception when trying to pass a df to `resource()`…
-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…
-
```
Flying saucer uses strings for uris in UserAgentCallback. This would normally
allow transparent handling of custom uris like virtual:// to map "virtual"
resources to real resources.
Unfortunate…