Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 9 of 9 total |
Index identifier problem |
Mon, Jun 16 2008 10:07 AM | Permanent Link |
Heiko Knuettel | When executing the query
CREATE INDEX "aartnr;pnr" ON "saartpar" ("aartnr", "pnr") I get an Error #406 invalid index identifier 'aartnr;pnr' Is the ";" the problem ? In DBISAM I always used the FieldExpression as IndexName...and it would be nice to continue so. The manual says "Identifiers may contain may contain any non-symbolic or punctuation character in the ANSI character set" Am I missing something ? |
Mon, Jun 16 2008 10:23 AM | Permanent Link |
ulibecker | Heiko,
<< CREATE INDEX "aartnr;pnr" ON "saartpar" ("aartnr", "pnr") I get an Error #406 invalid index identifier 'aartnr;pnr' >> The syntax is not correct for EDB. CREATE TEXT INDEX <Name> ON <TableName> (<ColumnName> [COLLATE <CollationName>]) [DESCRIPTION <Description>] [INDEXED WORD LENGTH <WordLength>] [FILTER TYPE COLUMN <ColumnName>] [WORD GENERATOR <WordGeneratorName>] In your case it should be: CREATE INDEX "MyIndex" ON "saartpar" ("aartnr", "pnr") MyIndex is the Name, saartpar the TableName, aartnr and pnr the column names. Uli |
Mon, Jun 16 2008 10:42 AM | Permanent Link |
Heiko Knuettel | >>CREATE INDEX "MyIndex" ON "saartpar" ("aartnr", "pnr") >>MyIndex is the Name, saartpar the TableName, aartnr and pnr the column names. I know. But what if I want "aartnr;pnr" to be the index name ? |
Mon, Jun 16 2008 10:46 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Heiko,
<< Is the ";" the problem ? >> Yes. << In DBISAM I always used the FieldExpression as IndexName...and it would be nice to continue so. The manual says "Identifiers may contain may contain any non-symbolic or punctuation character in the ANSI character set" >> ';' is a punctuation character: http://owl.english.purdue.edu/handouts/grammar/g_overvw.html -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Jun 16 2008 10:51 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Heiko,
<< The manual says "Identifiers may contain may contain any non-symbolic or punctuation character in the ANSI character set" >> Actually, I see how that can be misinterpreted. It should read: Identifiers may contain any non-symbolic or non-punctuation character in the ANSI character set I've corrected this in the manual. The reason for the non-punctuation is the problems that it can cause with parsing. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Jun 16 2008 10:54 AM | Permanent Link |
Heiko Knuettel | OK, thanks
|
Mon, Jun 16 2008 10:56 AM | Permanent Link |
"Raul" | Actually manual says "Identifiers may contain any non-symbolic or non-punctuation character..." - technically semicolon that you are using is punctuation thus not allowed by this statement. Raul "Heiko Knuettel" <heiko@knuettel.com> wrote in message news:05A4B0AB-1957-41B8-855E-ECF9A0BCEC6C@news.elevatesoft.com... > When executing the query > > CREATE INDEX "aartnr;pnr" ON "saartpar" ("aartnr", "pnr") > > I get an Error #406 invalid index identifier 'aartnr;pnr' > > > Is the ";" the problem ? In DBISAM I always used the FieldExpression as > IndexName...and it > would be nice to continue so. > The manual says "Identifiers may contain may contain any non-symbolic or > punctuation > character in the ANSI character set" > > Am I missing something ? > |
Mon, Jun 16 2008 10:59 AM | Permanent Link |
"Raul" | Never mind - looks like Tim just fixed it and i was reading the online
manual. Talk about fast service! Raul "Raul" <raul@raul.ca> wrote in message news:288F0E7B-238B-43FB-B17E-60CADB526BE1@news.elevatesoft.com... > > Actually manual says "Identifiers may contain any non-symbolic or > non-punctuation character..." - technically semicolon that you are using > is punctuation thus not allowed by this statement. > > Raul > > > "Heiko Knuettel" <heiko@knuettel.com> wrote in message > news:05A4B0AB-1957-41B8-855E-ECF9A0BCEC6C@news.elevatesoft.com... >> When executing the query >> >> CREATE INDEX "aartnr;pnr" ON "saartpar" ("aartnr", "pnr") >> >> I get an Error #406 invalid index identifier 'aartnr;pnr' >> >> >> Is the ";" the problem ? In DBISAM I always used the FieldExpression as >> IndexName...and it >> would be nice to continue so. >> The manual says "Identifiers may contain may contain any non-symbolic or >> punctuation >> character in the ANSI character set" >> >> Am I missing something ? >> > > |
Mon, Jun 16 2008 11:20 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Raul,
<< Never mind - looks like Tim just fixed it and i was reading the online manual. >> Sorry about that. Our manuals are "live", so when I fix something the web site immediately reflects the change. << Talk about fast service! >> It's easier to just fix it right away. I'm bad enough in the procrastination department as it is without making it worse. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |