Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 9 of 9 total |
Little issue with statement termination character |
Sat, Mar 3 2012 12:46 PM | Permanent Link |
Tiago Ameller Menorca Zeros i Uns SL | There is a little issue almost from 2.05b11. If you try to execute
some DDL sentences separated by a configured char in preferences (default is !, but also test with | (pipping)), you get a error "ElevateDB Error #700 An error was found in the statement at line 29 and column 30 (Expected end of expression but instead found !)" I'm surprised there are no incident reports about this, and Tim says he can't reproduce it. Anybody with the same issue? To reproduce it: 1.In a fresh machine (I used a VM one), install edbmgr 2.Create a remote connection to an existing server 3.Open an existing remote database 4.Paste any code formed by a couple of SQL sentences (below a sample) I think if fails when pasting more than writing. CREATE TEMPORARY TABLE "XTMLIAMAS" ( "Codigo" SMALLINT NOT NULL, "Nombre" VARCHAR(80) COLLATE "ESP_CI_AI" NOT NULL, "Comentario" CLOB COLLATE "ESP_CI_AI", "Tipo" SMALLINT DEFAULT 0 NOT NULL DESCRIPTION '0 = SQL 1 = StoredProc', "SQLText" CLOB COLLATE "ANSI", "SumFields" VARCHAR(1024) COLLATE "ANSI", "Aviso" BLOB, "Bloqueado" BOOLEAN DEFAULT FALSE NOT NULL, "FechaAlta" TIMESTAMP DEFAULT CURRENT_TIMESTAMP DESCRIPTION 'Fecha Alta', "UsuarioAlta" SMALLINT DEFAULT 1 NOT NULL DESCRIPTION 'Usuario Alta', "FechaMod" TIMESTAMP DESCRIPTION 'Fecha Modificado', "UsuarioMod" SMALLINT DEFAULT 0 , "CodigoLog" INTEGER GENERATED ALWAYS AS IDENTITY (START WITH 1, INCREMENT BY 1) DESCRIPTION 'Código Auditoría', CONSTRAINT "PrimaryKey" PRIMARY KEY ("Codigo") ) DESCRIPTION 'Cabecera de listados y avisos' VERSION 1.00 READWRITE UNENCRYPTED INDEX PAGE SIZE 4096 BLOB BLOCK SIZE 512 PUBLISH BLOCK SIZE 512 PUBLISH COMPRESSION 0 MAX ROW BUFFER SIZE 32768 MAX INDEX BUFFER SIZE 65536 MAX BLOB BUFFER SIZE 32768 MAX PUBLISH BUFFER SIZE 32768! INSERT INTO "XTMLIAMAS" VALUES (10, 'Servicios por meses', NULL, 0, 'select extract(year from fecha) as Año, extract(month from fecha) AS Mes, count(*) AS Servicios from hojaruta group by extract(year from fecha), extract(month from fecha) order by extract(year from fecha), extract(month from fecha) ', 'Servicios', NULL, FALSE, TIMESTAMP '2011-12-20 13:41:16.0390', 1, NULL, 0, 2)! |
Sun, Mar 4 2012 8:44 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tiago
Just tried it here in 2.06b2 and it runs fine Roy Lambert [Team Elevate] |
Sun, Mar 4 2012 10:41 AM | Permanent Link |
Tiago Ameller Menorca Zeros i Uns SL | Roy,
<Just tried it here in 2.06b2 and it runs fine> Thanks for testing it. I use Spanish locale and ANSI EDB server and client. Using VMware XP SP2 machines for testing and development. It's very, very strange, but this new feature never worked for me. I like it a lot, due DBISAM had it always (v2 in scripting, v3+ in normal SQL editor) and it's very useful. Hope somebody else can reproduce it Tiago |
Sun, Mar 4 2012 11:39 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tiago
My memory (which is highly suspect these days) is telling me that this is an enhancement built into EDBManager rather than the core engine. If that's right you should be able to investigate some more on your side. With you mentioning you're using Spanish I wonder if it has something to do with that and ! not being the same as EDBManager is expecting eg if Tim's programmed it in to look for #33 and the ! isn't at that point in the Spanish character set. Roy Lambert [Team Elevate] |
Mon, Mar 5 2012 11:36 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< With you mentioning you're using Spanish I wonder if it has something to do with that and ! not being the same as EDBManager is expecting eg if Tim's programmed it in to look for #33 and the ! isn't at that point in the Spanish character set. >> We just use whatever character is specified in the Preferences dialog (Editor tab) as the statement terminator character. It's handled as a Char, so should always resolve to the same code point, given that everything is using the system locale under Windows (which it is). -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Mar 5 2012 3:42 PM | Permanent Link |
Tiago Ameller Menorca Zeros i Uns SL | Tim,
Are you sure server side has no effect in parsing? It's very weird nobody can't reproduce it. I haven't configured a fresh server, just using same version than client, but this is a remote server installed in the early days of ElevateDB, updated with every release over same set of databases and configuration. I'll try again in a customer installation, but i remember also it fails in a customer environment. |
Tue, Mar 6 2012 6:47 AM | Permanent Link |
Tiago Ameller Menorca Zeros i Uns SL | Hi again:
I guess got how to reproduce: it fails when click "prepare" button, not when click "execute". But when has failed, all "execute" also fails until exit from manager. Open a new editor, type some sentences with terminator, click prepare (not execute). Regards, |
Tue, Mar 6 2012 7:43 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Tiago
Congratulations on finding it. Now Tim just has to fix it Roy Lambert |
Wed, Mar 21 2012 3:06 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Tiago,
<< I guess got how to reproduce: it fails when click "prepare" button, not when click "execute". But when has failed, all "execute" also fails until exit from manager. >> Thanks, I'll have a fix for this in the next build. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 5, 2024 at 10:18 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |