entity framework - EF5 generates SQL Server CE constraints with dot in name -


i building .net disconnected client-server application uses entity framework 5 (ef5) generate sql server ce 4.0 database pocos. application allows user perform bulk copy of data network sql server client's sql server ce database. (very) slow, due constraints , indexes created ef5. temporarily dropping constraints , indexes reduce 30-minute wait 1 minute or less.

before starting bulk copy, application executes queries drop constraints , indexes sql server ce tables. however, commands fail, because ef5 created constraint names include table schema name, dot, , table name. dot in constraint name causing drop command fail, due parsing issue.

for example, poco customer creates table dbo.customer primary key constraint pk_dbo.customer_id. database performs expected.

however, upon executing non-query:

 alter table customer drop constraint pk_dbo.customer;

sql server compact ado.net data provider returns error:

there error parsing query.
[ token line number = 1, token line offset = 57, token in error = . ]

of course, using secondary datacontext object not have foreign keys generate database without constraints, , add them later works; but, requires maintaining 2 datacontext objects , not forgetting keep both updated. therefore, looking 1 of 2 solutions:

  1. compose drop statement in such way . character parsed

  2. prevent ef5 using . character in constraint , index names

thank in advance help!

wrap bad boy in []. tells parser inside key name. 

alter table customer drop constraint [pk_dbo.customer];

should run fine. wrap every identifier in brackets avoid exact issue. write query this.

alter table [customer] drop constraint [pk_dbo.customer];

i think it's more readable way because can instantly see identifiers.


-

Comments

Post a Comment

Popular posts from this blog

PySide and Qt Properties: Connecting signals from Python to QML -

i trying run simple pyside appliccation design made in qml. call function in qml python in separated thread. i have following qml view: import qt 4.7 rectangle { visible: true width: 100; height: 100 color: "lightgrey" text { id: datestr objectname: "datestr" x: 10 y: 10 text: "init text" font.pixelsize: 12 function updatedata(text) { datestr.text = qstr(text) console.log("you said: " + text) } } } here application: some imports.... #!/usr/bin/python import sys import time pyside import qtdeclarative, qtcore pyside.qtgui import qapplication pyside.qtdeclarative import qdeclarativeview the qthread worker.... #worker thread class worker(qtcore.qthread): updateprogress = qtcore.signal(int) def __init__(self, child): qtcore.qthread.__init__(self) self.child = child def run(self):
Read more

c# - DevExpress.Wpf.Grid.InfiniteGridSizeException was unhandled -

Image
when using devexpress, see error: devexpress.wpf.grid.infinitegridsizeexception unhandled message="by default, infinite grid height not allowed since grid rows rendered , hence grid work slowly. fix issue, should place grid container give finite height grid, or should manually specify grid's height or maxheight. note can avoid exception setting gridcontrol.allowinfinitegridsize static property true, in case grid run slowly." the problem dxgrid has infinite height. to fix, set height non-infinite. snoop absolutely invaluable this: if "height" xaml element infinite (i.e. 0 or nan ), can set using one of following: option 1: height="{binding path=actualheight, relativesource={relativesource mode=findancestor, ancestortype=uielement}}" option 2: verticalalignment="stretch" option 3: height="auto" hint: use verticalalignment="stretch" if child of grid <rowdefinition height=
Read more

scala - 'wrong top statement declaration' when using slick in IntelliJ -

Image
i'm porting project scala 2.9 2.10, therefore have use slick instead of scalaquery. i'm using slick 2.1.0 since supports ms access. according this tutorial , upgrade guide changed robs object class , added val robs : why error message wrong top statement declaration , how rid of it? edit: i'm new scala... according this question seems can't put val outside of methods or classes, right? code above directly in packge. right approach slick then? should move code in class or trait? according this changed val robs = tablequery[robs] to object robs extends tablequery(new robs(_)) {} . no warnings or errors anymore. :)
Read more