Hi,
Look at the old PBXT blob-streaming source. It is probably still very
useful.
--Justin
On Tue, Feb 3, 2015 at 9:18 PM, Roberto Spadim
wrote:
> ... i was thinking about big table results, internall network use, and
> optimization ...
> should be interesting, if we have a database-side way
... i was thinking about big table results, internall network use, and
optimization ...
should be interesting, if we have a database-side way to export data
directly to app-client
i'm thinking about a configuration like...
client app (conect)---> app server, app mysql client (connect)--->
Hi guys
I will comment Justin Swanhart mail, that's reasonable
>>Hi,
>>I suggest creating an MDEV spec for COLUMN_BSON() to return BSON data
which can handle binary (MongoDB uses it to store binary data).
Nice, solve a binary representation problem, maybe we will need
BSON_TO_COLUMN and JSON_TO_C
Hi,
I suggest creating an MDEV spec for COLUMN_BSON() to return BSON data which
can handle binary (MongoDB uses it to store binary data). In the same
MDEV, COLUMN_JSON should be modified to omit binary columns and return a
warning to use COLUMN_BSON for a complete representation of the data.
Doe
the warning is not for null, the warning is for column_json return not
strict to json specs
___
Mailing list: https://launchpad.net/~maria-discuss
Post to : maria-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~maria-discuss
More help
Hi!
On Tue, Feb 3, 2015 at 5:25 PM, Raina Masand <
cf-core-services-...@pivotal.io> wrote:
> Hello,
>
> We are looking to use Galera 25.3.9 with our MariaDB cluster, which claims
> to improve the stability of communication between nodes in the event of
> network flakiness. Do you know if it will
Hello,
Recently, we experienced a sudden failure on a 3-node MariaDB Galera
cluster (version 10.0.13), and can't find any documentation or discussion
of these particular logs. Prior to the crash, our cluster seemed to be
experiencing connectivity issues, and this particular node was partitioned
fr
Hello,
We are looking to use Galera 25.3.9 with our MariaDB cluster, which claims
to improve the stability of communication between nodes in the event of
network flakiness. Do you know if it will be compatible with MariaDB
10.0.16? The release notes for MariaDB Galera Cluster 10.0.16 seem to
sugge
i will give an example with uncompress:
SELECT UNCOMPRESS('abc')
return-> NULL
SHOW WARNINGS
"Level" "Code" "Message"
"Warning" "1259" "ZLIB: Dados de entrada está corrupto"
return NULL+warning
but that's not COLUMN_JSON
UNCOMPRESS receive a wrong input
COLUMN_JSON return a "wrong" output
with
Why a warning? NULL has a meaning that cannot be represented in other ways. A
missing death_date means that you John is alive. death_date=NULL means that we
don't know when John has died.
Representing an information in the only correct way should not cause a warning.
Redards
Federico
-
back to the question
What *should* COLUMN_JSON() do when a dynamic column contains BINARY
values?
today what should be expect?
return "wrong" (incompatible with json specs) json value?
return null+warning?
return "wrong"+warning?
i think it's a 'sql_mode' that should be set to strict or not
_
Wikipedia's explanation sounds like a way to say nothing, while still
pretending they are saying something. An information does not exist "in the
database"? This is obvious for anyone! I don't know a single person stupid
enough to think that NULL is a valid name or telephone number :) The open
Hi, Tom!
On Feb 03, Tom Worster wrote:
> Hi Sergei,
>
> On 2/3/15, 7:13 AM, "Sergei Golubchik" wrote:
>
> >> A dynamic column cannot be NULL, so using a JSON null (a different
> >> kind of null) to express "dynamic column exists but cannot be
> >> represented as requested" should work. The ORM
On 2/3/15, 10:24 AM, "Justin Swanhart" wrote:
>NULL and missing are two different concepts. Null means unknown, not
>missing. The data structure should have an ability to store NULL to be
>compatible with RDBMS semantics. While a dynamic column is similar to a
>NoSQL document store it is not o
NULL and missing are two different concepts. Null means unknown, not missing.
The data structure should have an ability to store NULL to be compatible with
RDBMS semantics. While a dynamic column is similar to a NoSQL document store
it is not one, and should support SQL semantics.
IMHO
--
Hi Sergei,
On 2/3/15, 7:13 AM, "Sergei Golubchik" wrote:
>> A dynamic column cannot be NULL, so using a JSON null (a different kind
>>of
>> null) to express "dynamic column exists but cannot be represented as
>> requested" should work. The ORM would then have the names and positions
>>in
>> the
On 03.02.15 13:13, Sergei Golubchik wrote:
[skip]
A dynamic column cannot be NULL, so using a JSON null (a different kind of
null) to express "dynamic column exists but cannot be represented as
requested" should work. The ORM would then have the names and positions in
the structure of all the B
Hi, Tom!
On Feb 01, Tom Worster wrote:
> Hi Sergei,
>
> base64 makes sense only if I store a base64 encoded value, which is what
> my ORM extension does (prefixed with
> 'data:application/octet-stream;base64,') for non-utf8 strings. So I say
> leave that to me.
Right...
> A dynamic column canno
18 matches
Mail list logo
