This helps avoid making your code dependent on the driver, so that you can change the underlying driver (and thus the database you’re accessing) with minimal code changes. (In our opinion, it’s usually a bad idea.) Instead, your code should only refer to types defined in database/sql, if possible. You generally shouldn’t use driver packages directly, although some drivers encourage you to do so. To use database/sql you’ll need the package itself, as well as a driver for the specific database you want to use. One consequence of this is that if you fail to release connections back to the pool, you can cause sql.DB to open a lot of connections, potentially running out of resources (too many connections, too many open file handles, lack of available network ports, etc). It’s safe for concurrent use by multiple goroutines.Ī connection is marked in-use when you use it to perform a task, and then returned to the available pool when it’s not in use anymore. The sql.DB abstraction is designed to keep you from worrying about how to manage concurrent access to the underlying datastore. It manages a pool of connections as needed, which may be a variety of things as mentioned.It opens and closes connections to the actual underlying database, via the driver.Sql.DB performs some important tasks for you behind the scenes: It also doesn’t map to any particular database software’s notion of a “database” or “schema.” It’s an abstraction of a database, which might be as varied as a local file, accessed through a network connection, or in-memory and in-process. The first thing you should know is that sql.DB isn’t a database connection. You use this type to create statements and transactions, execute queries, and fetch results. To access databases in Go, you use a sql.DB. Many of us find ourselves wishing for a quick reference and a “getting started” orientation that tells stories instead of listing facts. The package’s documentation tells you what everything does, but it doesn’t tell you how to use the package. It provides a lightweight interface to a row-oriented database. The idiomatic way to use a SQL, or SQL-like, database in Go is through the database/sql package. I encourage you to check it out for a comprehensive understanding of Go approach to SQL databases. I think if the undone projects can be put into a Microsoft Project file and worked piece by piece, they are a lot closer to becoming complete than just an idea in his and his assistant manager's head.This story is based on a great resource about using SQL in Go. This sounds really inefficient, perhaps from a project management perspective, but with such a small department, this is what I think will work for my new boss, to work undone project piece by piece until projects he's had sitting a mental shelf as onlyĪn idea will be put into a Microsoft Project file. Where I'm managing people with different skill sets that have to do 10 different things each day. In this file, I need to have a person as a "project phase" Task 1 for person 1 might be undone project 1, piece 1 task 2 person 1 might be undone project 9, piece 6 etc. My monthly or quarterly file will have employees listed with tasks The master project file will look like a normal project file. So I need to create a Project file that has a master project file that lists all the projects desired to be done. It's really not practical, even fiscally with such a small department to do formal project management. If there is such a thing, I need to show him how to manage by an informal project orientation. With no job experience in Project Management, and that I'm starting an MBA in Project Management! He wants me to give him project management ideas that will make his department operate in a manner that all his undone projects sitting on a mental shelf The manager has a basic knowledge of project management, saw that I had a BA in Project Management The department has less than 10 employees. My problem is that I will be starting work in 1 department within a larger non-profit, government funded program. Project file that starts and finishes in 1 month or 1 quarter of a year. The above drawn critical path image (roughly drawn in Word) will be not be on my master project file that lists desired projects as a project phase. Slack time available as each person finishes each task. I'll have a master file of numerous projects I want done during the year, that I plug away on, project piece by project piece depending on the When person 1 who performs task 1 finishes early I want to have them start another task of another project. This is what I want in description, though. Still can't post an image of what I want my critical path to look like with concurrent tasks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |