|
Bravo! especially for the UPSERT part.
But it would be even more interesting if it could also generate PostgreSQL code!
|
|
|
|
|
RickZeeland wrote: Bravo! especially for the UPSERT part.
That's actually configurable - you can tell the app not to combine the insert and update parts.
RickZeeland wrote: But it would be even more interesting if it could also generate PostgreSQL code!
I'm going to leave that as an exercise for another programmer. Besides that, you can easily inherit the generated class, and override the CRUD properties to support your own kind of chaos. 
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Quote: support your own kind of chaos
I already have enough chaos at hands thank you!
Should really try harder to work with NHibernate as that's what has been chosen as the standard where I work, but till now have been able to avoid implementing it in the projects I work on.
Also I should do some DevOppy things with Docker, but it seems to make no sense to use Docker with Windows, it's clearly a Linux thing
|
|
|
|
|
Thankfully, nobody on our team is enamoured with ORMs of any description. I can really understand the desire to have some of your more tedious code auto-magically generated, but ORMs impose to many proprietary ideas about how things should work, and how you should work with them, and it's often more tedious to find out how to get around those ideas than it is just to crank out your own code. This tool leans more towards the "crank out your own code" crowd. Even the viewmodel generator allows you to specify your own implementation of INotifyPropertyChanged and IDataErrorinfo (it provides my own implementation as a default, but the user can change it).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I think I would get flayed if I posted that much code in the lounge. 
Congratulations to you.
Real programmers use butterflies
|
|
|
|
|
Be careful what you say about JSOP, he's very dangerous
|
|
|
|
|
In American Texas, code poster flays you 
|
|
|
|
|
I don't see the problem with posting the output from a code generator, as long as you don't pose a question about it in the message. At that point, you're simply showing the output of an application. If anyone gives you grief, let me know - I'll set 'em straight.
Note - I purposely chose a table that only has a few returned columns.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I don't either, personally. I appreciated your comment, as I am a fan of code generation.
Real programmers use butterflies
|
|
|
|
|
JSOP is a special case, a bit like OG, the Richards and you for that matter. People who contribute so much to the site that they have and deserve carte blanche. It is very rarely abused.
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
That's fair. I try not to abuse the forum myself but I'm a weirdo and social decorum is not always my best strength, even online. Even among other developers. 
Real programmers use butterflies
|
|
|
|
|
Why not an article, or even a tip, where it stays in a more permanent place than this Lounge?
|
|
|
|
|
0) I've been here for 20 years. I know how to do this.
1) I'll write/publish the article when the code is done. I started the article last May when the code was reasonably complete, but lost a crap load of the code, and stopped working on it. As stated in the original message, I decided to start working on it again this week to rewrite the code I'd lost, and was merely sharing the progress.
2) Cool your jets, Sparky.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
CrudGet*
CrudUpsert*
CrudDelete*
I was going to ask why you didn't use a MERGE for the UPSERT, but I already found out myself. Good stuff! 
|
|
|
|
|
Sander Rossel wrote: I was going to ask why you didn't use a MERGE for the UPSERT, but I already found out myself.
Using the MERGE function is fraught with danger, and it's easy to do it wrong. Furthermore, a MERGE operation is usually more complex, and typically uses several of the table's columns to determine whether or not an item should be updated. There's probably no way to generate it automagically that would be suitable in more than a small handful of instances.
It is simply easier and more reliable to generate an Upsert instead.
The programmer can always extend the generated partial class and include a specific CRUDMerge property, so I think my bases are sufficiently covered. BTW, this is primary reason I'm writing this aapp - the existing tools don't create partial classes, and don't allow you to customize their implementation based on corporate requirements as far as coding style and framework component inclusion. For instance, you can specify your own implementation code for INotifyPropertyChanged, and IDataErrrorInfo interfaces in the generated viewmodel, and you can even specify the standard using statements for the model and viewmodel (although the usefulness of these would only benefit you if a given "standard" name space was removed from .Net at some point in the future).
It's a cool app, and we're going to use it at work when we start our flagship application rewrite (whenever that's allowed to happen).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
#realJSOP wrote: It's a cool app, and we're going to use it at work when we start our flagship application rewrite (whenever that's allowed to happen).
Good stuff!
I've been using Entity Framework Core and love it so far.
I just write my domain models, write my DB mapping and let EF sort out the rest.
Not so nice when you get breaking changes and EF just drops a column (or table) instead of renaming and that sort of stuff
The queries it generates are pretty clean overall and I've gotten a lot better at predicating what they look like based on my LINQ query 
|
|
|
|
|
The company I work for would flog you for using the NOLOCK hint in your SELECT statement.
Kelly Herald
Software Developer
|
|
|
|
|
Wehave simulateous access by thousands of users and dozens of stored procs, we have to do that because our queries take a few seconds.If we don't do it, we get errors.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
I decided to go for KeePass[^].
It's ugly.
But all is stored locally with high encryption, no need to connect to any server somewhere.
And even Bitwarden seems much nicer (aesthetically) I should have installed a docker container in my NAS to act as my personal server to avoid sending all my passwords into the cloud which seems too much overkill to me.
THANK YOU VERY MUCH everybody who posted an answer and a hint.
![Beer | [beer]](https://codeproject.freetls.fastly.net/script/Forums/Images/beer.gif)
|
|
|
|
|
Joan M wrote: It's ugly.
Take that back! The interface can be considered "old school" by today's standard, but it's compact and functional. To me it's the peak usability. None of that modern big flat and empty surfaces crap taking valuable screen real estate.
Look at this crap! Something like 70% of the screen is nothing. I understand developers not caring about performance and expecting users to throw more hardware at the problem, but that does not work with monitors... I mean at some point user's room will not be large enough to fit the screen needed to display your damn application.
|
|
|
|
|
Luckily Ultra-Wide monitors are getting more and more affordable!
|
|
|
|
|
Clearly you've not seen those futuristic films about hacking where the password occupies the whole 9000 inches screen the hacker has to use a command line interface.
|
|
|
|
|
God bless Mr. Robot for at least breaking from that mold somewhat.
Real programmers use butterflies
|
|
|
|
|
Agree.
|
|
|
|
|
Mladen Janković wrote: peak usability.
I like that.
I agree it's what a Win32 desktop app can be expected to look like. I think some people have just developed a twisted view of what an app should look like because they spend so much time on a freakin' phone.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
