Search found 6 matches

by iamnotcreative
Wed 27 Jul 2022 16:23
Forum: Entity Developer
Topic: Duplicate Designer File being created upon save
Replies: 1
Views: 8800

Duplicate Designer File being created upon save

Hello,

I'm running into a problem when editing my project's LQML in that it's creating a new .Designer.vb file upon Save All. I had previously edited one of the classes to put the schema in front of the table name and when I did that it removed the line

<LastGenOutput>MyProject.Designer.vb</LastGenOutput>

from the lqml section of my project file.

Code: Select all

<None Include="MyProject.lqml">
<Generator>DevartLinqToSqlGenerator</Generator>
<SubType>Designer</SubType>
</None>


I've tried manually editing my project file which work once after which the LastGenOutput line is removed again.

Running Devart Entity Developer- 6.12.1354.0 in Visual Studio 2019. Any help is appreciated.
by iamnotcreative
Fri 06 Nov 2020 20:46
Forum: Entity Developer
Topic: Entity Developer pulling Oracle Package Procedures in as stand alone procedures
Replies: 3
Views: 2356

Re: Entity Developer pulling Oracle Package Procedures in as stand alone procedures

Shalex wrote: Thu 05 Nov 2020 19:21 Thank you for your report. We have reproduced the issue and will notify you when it is fixed.
Thank you, I appreciate how quickly you looked into this matter.
by iamnotcreative
Thu 05 Nov 2020 18:16
Forum: Entity Developer
Topic: Entity Developer pulling Oracle Package Procedures in as stand alone procedures
Replies: 3
Views: 2356

Entity Developer pulling Oracle Package Procedures in as stand alone procedures

Hello,

I'm experiencing this with versions 6.9.1092 and 6.3.525, so I suspect it's something to do with us specifically instead of the program.

We recently updated to Oracle 18c Standard Edition 2 which is hosted on an AWS server. When I attempt to do Update Model in the LQML for our instance both versions are thinking procedures that exist in two different packages have been dropped, and that they instead exist as stand alone procedures. It only does this with procedures with no passed in parameters; procedures that have parameters show up under the package and all functions show up under the package regardless of if they have IN parameters or not.

I'm hoping someone else has run into this and knows the cause and the fix

Thank You
by iamnotcreative
Thu 25 Jul 2019 21:45
Forum: LinqConnect (LINQ to SQL support)
Topic: Manually set Identity field in Oracle
Replies: 2
Views: 5169

Re: Manually set Identity field in Oracle

To clarify, I am setting the ID column in the web.table object and then using the .InsertOnSubmit and .SubmitChanges methods in the Devart.Data.Linq.DataContext class
by iamnotcreative
Thu 25 Jul 2019 21:06
Forum: LinqConnect (LINQ to SQL support)
Topic: Manually set Identity field in Oracle
Replies: 2
Views: 5169

Manually set Identity field in Oracle

Hello everyone, I apologize in advance if this has already been asked.

We're a VB.Net shop with two Oracle databases, let's call one local and the other web. Local has a table with an ID column that is populated via a trigger, this works just fine in our code; the insert statement is generated correctly and the ID is brought back into the object. What I need to do is then take that ID value and use it in the INSERT statement that's being generated for inserting into the web database version of that same table. So basically:

Insert into local.table (foo, bar) values (:p1, :p2) returning ID into :ret1

Insert into web.table (id, foo, bar) values (:ret1, :p1, :p2)

Any help would be appreciated.
by iamnotcreative
Mon 19 Nov 2012 22:26
Forum: LinqConnect (LINQ to SQL support)
Topic: Oracle XMLType field being rewritten
Replies: 1
Views: 1150

Oracle XMLType field being rewritten

Hello,

We're using LinqConnect in a VB program written using Visual Studio 2010 to talk to an Oracle database. We have a table that consists of three columns: id, status and xmltext which is an XMLType field.

We ran into a problem where the XML was being rewritten after the status field, and only the status field, was updated. Things like tag order changing, empty elements being changed from <element></element> to <element /> and characters such as Ñ being turned into their Windows-1252 equivalent. Something I found out today is that the XML isn't completely proper as it's missing <?xml version="1.0" encoding="UTF-8"?> at the top but was wondering if it's even possible LinqConnect is doing this?