ols that design anti-pattern schema's people will use them, no
> one wins.
>
>
> On Tue, Mar 5, 2013 at 4:30 PM, Andrew Prendergast <
> a...@andrewprendergast.com
> > wrote:
>
> > *>
> >
> >
> http://www.edwardcapriolo.com/roller/edwardcapri
ys do not work? Or for
> > that matter, how are your dealing with the fact that a "primary key" in
> > cassandra is nothing like a "primary key" in a RDBMS?
> >
> > Generally under the impression that CRUD tools that auto-generate CQL
> > schema's can
>
> Generally under the impression that CRUD tools that auto-generate CQL
> schema's can give someone the rope to hang themselves.
>
> On Tue, Mar 5, 2013 at 3:46 PM, Andrew Prendergast <
> a...@andrewprendergast.com
> > wrote:
>
> > Hi Tristan,
> &
Hi Tristan,
I've spent the last couple weekends testing the CRUD DML stuff and its very
close to meeting that objective (although NULL handling needs some tuning).
The main hiccups are in the JDBC driver which I have been working through
with Rick - once he accepts my patches it'll be pretty soli
Sylvain,
All I'm trying to do is make Cassandra work with existing ETL, ORM &
desktop tools a bit better.
I think that is a worthy cause.
ap
On Tue, Mar 5, 2013 at 8:20 PM, Sylvain Lebresne wrote:
> > This is just one of a few small adjustments that can be made to the
> grammar
> > to make e
Hi Sylvain,
I disagree. Actually, CQL3 is really close to being a faithful subset of
ANSI-SQL, which is rather exciting.
This is just one of a few small adjustments that can be made to the grammar
to make everyone's life easier while still maintaining the spirit of NOSQL.
The semantics of how th
> On Sat, Mar 2, 2013 at 12:19 PM, Michael Kjellman
> wrote:
>
> > Might want to create a Jira ticket at issues.apache.org instead of
> > submitting the bug report thru email.
> >
> > On Mar 2, 2013, at 3:11 AM, "Andrew Prendergast" <
> a...@andrewprende
Just posting this as more of a talking point around comparing the behavior
of classical RDMBS to Cassandra. This bug is fixable over in the JDBC
driver, but look at isolation #2 & exception B:
http://code.google.com/a/apache-extras.org/p/cassandra-jdbc/issues/detail?id=72
It's coming from the ser
*DESCRIPTION*
When creating a table in all ANSI-SQL compliant RDBMS' the VARCHAR datatype
takes a numeric parameter, however this parameter is generating errors in
CQL3.
*STEPS TO REPRODUCE*
CREATE TABLE test (id BIGINT PRIMARY KEY, col1 VARCHAR(256)); // emits Bad
Request: line 1:54 mismatched
