I agree! We should not force people to use a special name-convention!
But, IMHO, if we know, from long time of experience, that a table-name like
New Query Layer
can cause problems
we should not force to use this name
by offer them as a good table-name.
uwe
Am 11.04.2013 13:35, schrieb edgar.so
thanks, while not the standard document itself, at least they claim to cite it.
anyway, i am on par with Michael on that. it should be optional and implemented
on writing to a DBMS connection.
..ede
PS: i am totally with that using alnum and underscore is the most common
denominator and usuall
Hi Ede,
maybe this helps:
http://pubs.vmware.com/vfabric5/index.jsp?topic=/com.vmware.vfabric.sqlfire.1.0/reference/language_ref/sql_identifiers.html
All I like to say is that
delimited identifiers
can cause problems.
If you like delimited identifiers
use them!
Uwe
Am 11.04.2013 11:19, schrie
On 11.04.2013 08:34, Uwe Dalluege wrote:
SNIP
>
>> There is no restriction too, as tables are created with quoted
>> strings which accept any character (but maybe it is not a so
>> common habit among DB adm, and I don't know if quoted
>> strings for table or column names is part of the SQL standar
Hi Michaël,
Am 10.04.2013 22:30, schrieb Michaël Michaud:
> Hi,
>
> Original question was about the Layer Name of Run Datastore Query.
>
> But Layer Name is a OpenJUMP thing.
> There is no restriction about how to write a Layer Name and many
> OpenJUMP plugin write layer names with spaces.
>
> I g
Hi,
Original question was about the Layer Name of Run Datastore Query.
But Layer Name is a OpenJUMP thing.
There is no restriction about how to write a Layer Name and many
OpenJUMP plugin write layer names with spaces.
I guess your problem is that this layer name will be used again
when you'll t
thanks Jukka.
all i am saying is: the DBMS enforces this restriction so it should be
implemented when writing to it, not when creating a new layer from a resultset,
possibly even from another DBMS.
..ede
On 10.04.2013 15:55, Rahkonen Jukka wrote:
> Hi,
>
> Just tried the following with Postg
Hi,
Just tried the following with PostgreSQL and table was created. I do not know
if it works with all versions and I agree that using spaces in table names is
not a brilliant idea.
CREATE TABLE "test space" as select * from table limit 1;
-Jukka-
edgar.sol...@web.de wrote:
> On 10.04.2013
On 10.04.2013 13:41, Uwe Dalluege wrote:
> Hi,
>
> Am 10.04.2013 11:27, schrieb edgar.sol...@web.de:
>> On 10.04.2013 11:15, Uwe Dalluege wrote:
>>> Hi,
>>>
>>> is it possible to change the
>>> default Layer Name of
>>> "Run Datastore Query"
>>> to a valid SQL table name?
>>>
>>> An inexperienced
Hi,
Am 10.04.2013 11:27, schrieb edgar.sol...@web.de:
> On 10.04.2013 11:15, Uwe Dalluege wrote:
>> Hi,
>>
>> is it possible to change the
>> default Layer Name of
>> "Run Datastore Query"
>> to a valid SQL table name?
>>
>> An inexperienced user with SQL
>> maybe do not know that
>> "New Query La
On 10.04.2013 11:15, Uwe Dalluege wrote:
> Hi,
>
> is it possible to change the
> default Layer Name of
> "Run Datastore Query"
> to a valid SQL table name?
>
> An inexperienced user with SQL
> maybe do not know that
> "New Query Layer" is not a valid
> layername (SQL-Tablename).
>
i'd rather s
Hi,
is it possible to change the
default Layer Name of
"Run Datastore Query"
to a valid SQL table name?
An inexperienced user with SQL
maybe do not know that
"New Query Layer" is not a valid
layername (SQL-Tablename).
Thanks.
Uwe
---
12 matches
Mail list logo
