Hi!
Sergei == Sergei Golubchik ser...@pisem.net writes:
Sergei Hi,
Sergei we've talked about engine attributes in the CREATE TABLE,
Sergei and that one should be able to specify them per partition as well.
Sergei Now, thinking about it, I'm not quite sure what the semantics shuld be.
Sergei
Hi, Sergei!
My use case is 1.
- my use case start -
Currently,
Spider and Vertical Partitioning engine can use
table level connection, table level comment,
partition level comment and sub-partition level comment
for engine options.
This options have following priority.
1. sub-partition
On Wed, May 12, 2010 at 2:11 PM, kentoku kentokush...@gmail.com wrote:
Additionally,
for supporting different engines in different partitions,
table options should better to be added engine names like
global/session parameters for avoiding conflicting option names.
- example start -
Hi,
we've talked about engine attributes in the CREATE TABLE,
and that one should be able to specify them per partition as well.
Now, thinking about it, I'm not quite sure what the semantics shuld be.
What is your use case ? How do you want them to work ?
I see different possibilities. Say,
On Tue, May 11, 2010 at 12:05 PM, Sergei Golubchik ser...@pisem.net wrote:
Hi,
we've talked about engine attributes in the CREATE TABLE,
and that one should be able to specify them per partition as well.
Now, thinking about it, I'm not quite sure what the semantics shuld be.
What is your
Hi, Henrik!
On May 11, Henrik Ingo wrote:
On Tue, May 11, 2010 at 12:05 PM, Sergei Golubchik ser...@pisem.net wrote:
we've talked about engine attributes in the CREATE TABLE, and that
one should be able to specify them per partition as well.
Now, thinking about it, I'm not quite sure
6 matches
Mail list logo
