Re: Porting issues

[Tobias Downer <toby@xxxxxxxxx>]

Tim Pizey wrote:
> 
> Field names do not need to be quoted unless the name is a reserved word,
> the example that
> I encountered was trying to create a field called unique.

This is a limitation of the parser.  I know that other SQL interpreters
allow reserved words as field names without quotes.


> > > Postgresql uses INT where mckoidb uses integer
> >
> > Do you think it would be useful if I add this as an alias?  Are there
> > any other aliases that would be useful?
> 
> I have worked around, so not a problem for me, I think abreviabtions are
> for people who can't type
> so prefer your full integer.

I still think this would be worthwhile to add.  I've made this mistake
myself.

 
> > > Current sticking point is that the following is not valid mckoi sql:
> > > CREATE UNIQUE INDEX columninfo_id_index ON columninfo (id)
> >
> > Yes, the grammar does not understand 'create index' because indexing is
> > handled in a non-standard way by the engine (to be really picky - I
> > don't believe the SQL-92 standard defines indexing anyway).  The reasons
> > are documented on the mailing list.  Basically, my plan was for the
> > engine to manage indexes transparently with perhaps a few hints from the
> > database administrator.  Currently, by default every column gets an
> > index.
> 
> Perhaps you could add 'create index' as a no-op?
> 
> I will see if I can modify Melati so that if the db is mckoi then
> indexes are not applied,
> but I think this may be difficult.

I'll add this as a no-op for the next release.

Toby.

---------------------------------------------------------------
Mckoi SQL Database mailing list  http://www.mckoi.com/database/
To unsubscribe, send a message to mckoidb-unsubscribe@mckoi.com