Gleipnir/nidus-sync
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
nidus-sync/db/dbinfo/fieldseeker.timecard.bob.go

423 lines
10 KiB
Go
Raw Normal View History

Add ability to make LLM agent forget the conversation history This is extremely useful for testing. In order to do this I needed to actually deploy the migration to a bob fork so I could start to add support for behaviors I really want. Specifically the ability to search for ids in a slice.
2026-01-27 18:44:02 +00:00
// Code generated by BobGen psql v0.42.5. DO NOT EDIT.
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
// This file is meant to be re-generated in place and/or deleted at any time.
package dbinfo
import "github.com/aarondl/opt/null"
var FieldseekerTimecards = Table[
fieldseekerTimecardColumns,
fieldseekerTimecardIndexes,
fieldseekerTimecardForeignKeys,
fieldseekerTimecardUniques,
fieldseekerTimecardChecks,
]{
Schema: "fieldseeker",
Name: "timecard",
Columns: fieldseekerTimecardColumns{
Objectid: column{
Name: "objectid",
DBType: "bigint",
Make fieldseeker tables key on globalid, version This is because the objectid is not unique between organizations.
2026-01-13 04:16:24 +00:00
Default: "",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Comment: "",
Nullable: false,
Generated: false,
AutoIncr: false,
},
Activity: column{
Name: "activity",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
DBType: "character varying",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is ACTIVITY",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Startdatetime: column{
Name: "startdatetime",
DBType: "timestamp without time zone",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is STARTDATETIME",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Enddatetime: column{
Name: "enddatetime",
DBType: "timestamp without time zone",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is ENDDATETIME",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Comments: column{
Name: "comments",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is COMMENTS",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Externalid: column{
Name: "externalid",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is EXTERNALID",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Equiptype: column{
Name: "equiptype",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
DBType: "character varying",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is EQUIPTYPE",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Locationname: column{
Name: "locationname",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is LOCATIONNAME",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Zone: column{
Name: "zone",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is ZONE",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Zone2: column{
Name: "zone2",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is ZONE2",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Globalid: column{
Name: "globalid",
DBType: "uuid",
Make GlobalID required for all Fieldseeker tables I'm pretty sure it has to be there, and it allows me to clean up my code.
2026-01-05 02:28:28 +00:00
Default: "",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is GlobalID",
Make GlobalID required for all Fieldseeker tables I'm pretty sure it has to be there, and it allows me to clean up my code.
2026-01-05 02:28:28 +00:00
Nullable: false,
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Generated: false,
AutoIncr: false,
},
CreatedUser: column{
Name: "created_user",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is created_user",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
CreatedDate: column{
Name: "created_date",
DBType: "timestamp without time zone",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is created_date",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
LastEditedUser: column{
Name: "last_edited_user",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is last_edited_user",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
LastEditedDate: column{
Name: "last_edited_date",
DBType: "timestamp without time zone",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is last_edited_date",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Linelocid: column{
Name: "linelocid",
DBType: "uuid",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is LINELOCID",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Pointlocid: column{
Name: "pointlocid",
DBType: "uuid",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is POINTLOCID",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Polygonlocid: column{
Name: "polygonlocid",
DBType: "uuid",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is POLYGONLOCID",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Lclocid: column{
Name: "lclocid",
DBType: "uuid",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is LCLOCID",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Samplelocid: column{
Name: "samplelocid",
DBType: "uuid",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is SAMPLELOCID",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Srid: column{
Name: "srid",
DBType: "uuid",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is SRID",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Traplocid: column{
Name: "traplocid",
DBType: "uuid",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is TRAPLOCID",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Fieldtech: column{
Name: "fieldtech",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is FIELDTECH",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Creationdate: column{
Name: "creationdate",
DBType: "timestamp without time zone",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is CreationDate",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Creator: column{
Name: "creator",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is Creator",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Editdate: column{
Name: "editdate",
DBType: "timestamp without time zone",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is EditDate",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Editor: column{
Name: "editor",
DBType: "character varying",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is Editor",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Nullable: true,
Generated: false,
AutoIncr: false,
},
Rodentlocid: column{
Name: "rodentlocid",
DBType: "uuid",
Default: "NULL",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "Original attribute from ArcGIS API is RODENTLOCID",
Nullable: true,
Generated: false,
AutoIncr: false,
},
Geometry: column{
Name: "geometry",
DBType: "jsonb",
Default: "",
Comment: "",
Nullable: false,
Generated: false,
AutoIncr: false,
},
Geospatial: column{
Name: "geospatial",
DBType: "geometry",
Default: "NULL",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Comment: "",
Nullable: true,
Generated: false,
AutoIncr: false,
},
Initially made it through full update with new fieldseeker schema
2025-12-05 23:11:57 +00:00
Version: column{
Name: "version",
DBType: "integer",
Default: "1",
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Comment: "",
Nullable: false,
Generated: false,
AutoIncr: false,
},
OrganizationID: column{
Name: "organization_id",
DBType: "integer",
Default: "",
Comment: "",
Initially made it through full update with new fieldseeker schema
2025-12-05 23:11:57 +00:00
Nullable: false,
Generated: false,
AutoIncr: false,
},
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
},
Indexes: fieldseekerTimecardIndexes{
TimecardPkey: index{
Type: "btree",
Name: "timecard_pkey",
Columns: []indexColumn{
{
Make fieldseeker tables key on globalid, version This is because the objectid is not unique between organizations.
2026-01-13 04:16:24 +00:00
Name: "globalid",
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Desc: null.FromCond(false, true),
IsExpression: false,
},
Initially made it through full update with new fieldseeker schema
2025-12-05 23:11:57 +00:00
{
Name: "version",
Desc: null.FromCond(false, true),
IsExpression: false,
},
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
},
Unique: true,
Comment: "",
Initially made it through full update with new fieldseeker schema
2025-12-05 23:11:57 +00:00
NullsFirst: []bool{false, false},
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
NullsDistinct: false,
Where: "",
Include: []string{},
},
},
PrimaryKey: &constraint{
Name: "timecard_pkey",
Make fieldseeker tables key on globalid, version This is because the objectid is not unique between organizations.
2026-01-13 04:16:24 +00:00
Columns: []string{"globalid", "version"},
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Comment: "",
},
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
ForeignKeys: fieldseekerTimecardForeignKeys{
FieldseekerTimecardTimecardOrganizationIDFkey: foreignKey{
constraint: constraint{
Name: "fieldseeker.timecard.timecard_organization_id_fkey",
Columns: []string{"organization_id"},
Comment: "",
},
ForeignTable: "organization",
ForeignColumns: []string{"id"},
},
},
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
Comment: "",
}
type fieldseekerTimecardColumns struct {
Objectid column
Activity column
Startdatetime column
Enddatetime column
Comments column
Externalid column
Equiptype column
Locationname column
Zone column
Zone2 column
Globalid column
CreatedUser column
CreatedDate column
LastEditedUser column
LastEditedDate column
Linelocid column
Pointlocid column
Polygonlocid column
Lclocid column
Samplelocid column
Srid column
Traplocid column
Fieldtech column
Creationdate column
Creator column
Editdate column
Editor column
Rodentlocid column
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
Geometry column
Geospatial column
Initially made it through full update with new fieldseeker schema
2025-12-05 23:11:57 +00:00
Version column
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
OrganizationID column
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
}
func (c fieldseekerTimecardColumns) AsSlice() []column {
return []column{
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
c.Objectid, c.Activity, c.Startdatetime, c.Enddatetime, c.Comments, c.Externalid, c.Equiptype, c.Locationname, c.Zone, c.Zone2, c.Globalid, c.CreatedUser, c.CreatedDate, c.LastEditedUser, c.LastEditedDate, c.Linelocid, c.Pointlocid, c.Polygonlocid, c.Lclocid, c.Samplelocid, c.Srid, c.Traplocid, c.Fieldtech, c.Creationdate, c.Creator, c.Editdate, c.Editor, c.Rodentlocid, c.Geometry, c.Geospatial, c.Version, c.OrganizationID,
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
}
}
type fieldseekerTimecardIndexes struct {
TimecardPkey index
}
func (i fieldseekerTimecardIndexes) AsSlice() []index {
return []index{
i.TimecardPkey,
}
}
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
type fieldseekerTimecardForeignKeys struct {
FieldseekerTimecardTimecardOrganizationIDFkey foreignKey
}
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
func (f fieldseekerTimecardForeignKeys) AsSlice() []foreignKey {
Remove old FieldSeeker tables, use v2 generated tables. This requires a bunch of changes since the types on these tables are much closer to the underlying types of the Fieldseeker data we are getting back from the API. I now need to use proper UUID types everywhere, which means I had to modify the bob gen config to consistently use google UUID, my UUID library of choice. I also had to add the organization_id to all the fieldseeker tables since we rely on them existing for some of our compound queries. There were some changes to the API type signatures to get things to build. I may yet regret those.
2025-12-24 17:49:39 -07:00
return []foreignKey{
f.FieldseekerTimecardTimecardOrganizationIDFkey,
}
Move to latest bobgen, add fieldseeker schema references This is an intermediate step between shifting from the old fs_* prefixed table names to an entire fieldseeker schema. At this point we have both, and we aren't doing much with the new schema but compiling.
2025-12-02 00:28:14 +00:00
}
type fieldseekerTimecardUniques struct{}
func (u fieldseekerTimecardUniques) AsSlice() []constraint {
return []constraint{}
}
type fieldseekerTimecardChecks struct{}
func (c fieldseekerTimecardChecks) AsSlice() []check {
return []check{}
}
Reference in a new issue Copy permalink