sasha wrote:
Now you can see first problems. Look at properties of
_TestTableAdapter and you'll see that select, insert, update and
delete commands were generated successfully. Parameters types also correct.
Now look at properties of TestTableAdapter. It has only select
command. Rest
Mercea Paul wrote:
I have meet same problem.
SQL generated for update with designer generate error.
For Autonumber fields I modify allownull to true, and is autonumber to true.
For update statement, I have deleted all where blab la bla, and let only
where [EMAIL PROTECTED] and it works
Mercea Paul wrote:
I have meet same problem.
SQL generated for update with designer generate error.
For Autonumber fields I modify allownull to true, and is autonumber
to true.
For update statement, I have deleted all where blab la bla, and let
only
where [EMAIL PROTECTED] and it
It's because it's view. Neither provider for MS SQL generates update for view.
Maby it's MS SQL's provider issue ;-)
Yes, there's a problem. I'll try to look at it.
Thanks!
-
Take Surveys. Earn Cash. Influence the
now close editor and look at parameters collection and you'll see that
parameter @Int64 is of type Int32.
Yes, there's a problem. I'll try to look at it.
You know, what's really weird. Look at this (the test1 is your view Test):
ColumnName = INT64
ColumnOrdinal = 1
ColumnSize = 8
sasha wrote:
Maby it's MS SQL's provider issue ;-)
If somethink goes wrong, the MS SQL Provider is base for any other decisions.
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-
Take
sasha wrote:
CREATE TABLE _Test (Id INT PRIMARY KEY, Int64 BIGINT, String
VARCHAR(100));
I've found another interesting feature.
For table, if you create it like yours, you get 3 params for Int64 - Int64,
Original and _Null. Two first are right System.Int64, the 3rd (for null) is
Int32.
Didn't you find who delete quotes when command formatting?
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT business topics
sasha wrote:
Didn't you find who delete quotes when command formatting?
I don't have to find it. I know it. VS is the wrong man.
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-
Take
Hello:
Any ideas Carlos? This is really weird (but as usuall, it will some small
easy-to-fix problem).
I will try to review it this weekend, but if FbCommandBuilder,
FbConnection.GetSchema, and FbDataReader.GetSchema returns correct info
it's going to be hard to find were the problem is
Nice, but this helps us like saying true=true. If I'm not able to get this
on my sources it's unfixable.
Can you provide some steps how to reproduce this bug?
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
Can you provide some steps how to reproduce this bug?
Seems i understood why you can't reproduce the bug. I think you tried
reproduce it on tables, but i'm using views and seems on tables all
works completely diffirent.
So:
1) open your databse and create table like this:
3) Create
And yet one inconvenience. Seems designer knows what fields in table are
primary keys. So why don't it generates UPDATE and DELETE commands
using only this keys in WHERE clause:
... WHERE Id = @Original_Id;
?
-
Take
I'll loose a part of text. So
1) open your databse and create table like this:
CREATE TABLE _Test (Id INT PRIMARY KEY, Int64 BIGINT, String
VARCHAR(100));
2) Create view like this:
CREATE VIEW Test AS SELECT * FROM _Test;
Hello:
If i remember well, i was tracking the problem with Int64 parameters time
ago without success,
as looks like the FbCommandBuilder is returning correct info for them, the
same for the schema
and DataReader.GetSchema methods
I will try to give another try this weekend.
--
Un saludo
15 matches
Mail list logo
